We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
既然 BHContext 和 BeeHive 都被设计成单例,为什么 BeeHive 还需要依赖注入 context ?
[BHContext shareInstance].env = BHEnvironmentDev; //定义应用的运行开发环境 [BHContext shareInstance].application = application; [BHContext shareInstance].launchOptions = launchOptions; [BHContext shareInstance].moduleConfigName = @"BeeHive.bundle/CustomModulePlist";//可选,默认为BeeHive.bundle/BeeHive.plist [BHContext shareInstance].serviceConfigName = @"BeeHive.bundle/CustomServicePlist";//可选,默认为BeeHive.bundle/BHService.plist [[BeeHive shareInstance] setContext:[BHContext shareInstance]];
The text was updated successfully, but these errors were encountered:
设计上存在不合理性,欢迎来修改~
Sorry, something went wrong.
No branches or pull requests
既然 BHContext 和 BeeHive 都被设计成单例,为什么 BeeHive 还需要依赖注入 context ?
The text was updated successfully, but these errors were encountered: