Hi,

I've tried to use the new 4.0.2 release but there were some API changes that I cannot understand. Some of them cause the app to crash.

Here goes a list of issues:

TyphoonAssemblyActivator was deprecated.

Some of our assemblies are not listed in the plist file and thus, we have the following code to manually activate them.

@interface FactoryAssembly : TyphoonAssembly

Analyzer.Analyze returns, beside diagnostic warnings, diagnostic info messages as well.

It can be useful to add an additional info message that notes the case where a conditional registration is never used. Conditional registrations will be picked in order and can be selected using a predicate,

I am currently having a some confusion around the best implementation of my factory. I have created a Gist of 3 possible options.

1. Is widely viewed as a Service Locator which most people on the internet consider an anti pattern.
2. Appears to be the accepted method of working around the above pattern. However not to many p

Idea of this issue is to create an example on how to use Dependency Injector with Orator ORM.

Originally, this question was brought in #230.

Acceptance criteria:

• There is an example mini application showing how to use Dependency Injector and Orator ORM
• Mini application demonstrates benefits of using Dependency Injector and Orator ORM
• Description of that mini applicatio

关于接下来要写什么：

你们在这个时间点看到的文章已经把Laravel的Database部分都讲完了，接下来的计划是：

事件系统、用户认证系统、异常处理、Session以及Laravel应用请求整个生命周期的总结，当然我也想把
Composer原理和Laravel中用到的设计模式说一下以便更好的理解。时间来到了6月，希望能在18年把Laravel这些核心相关的东西大体梳理完，把年初挖的这个坑填上。

关于问题反馈和交流：
我在写这些文章时都会尽量严谨防止由于自己的失误误导大家，有的部分源码过多也就难免会有贴上了大块源码的地方，如果有看不懂的也欢迎针对话题新开issue来讨论。

Weaver's documentation lacks guidance about how to solve dependency cycles.

The most common case is for delegate patterns, which can be solved by using a self reference.

Other types of cycles (ones described in #140) aren't allowed by Weaver, and the documentation should show how to work around them.

• Work with posts
• Work with comments
• Work with user
• Using Search
• Using chat service
• Using tag
• Working with profile

Service error are the facility that output an error message when a service definition is not well formed, or it's usage with the container is invalid. Each time new checks are added and each time there's a new feature, we get regressions in the quality of error messages.

We should add tests that checks if the right error is outputted for particular case. It wil prevent regressions in the futur

For example:

How is TypesThat used?
How do we correctly use ExportAssembly

More samples regarding fluent API usage.

For example, I did this:

To register all the Tools in a given assembly as Tool, so an injection like IEnumerable<Tool> works I did:

registrationBlock.Export(toolType.Assembly.ExportedTypes
        .Where(TypesThat.AreBasedOn<Tool>())
        .Where

Should enhance the document for users to reduce learning cost of SwinjectStoryboard. Both of the following topics need some investigation for documentation.

• Availability with Storyboards and XIBs.
• Combination with Assembler.

Swinject/Swinject#95

People suggested to add some inline documentation because they have problems to understand how the library works. This should be fixed.

As disco is already hosted on github, wouldn't it be a great idea to serve the disco-documentation (that is currently only available via a local server) via github pages?

AFAIK that would require enabling the github-pages for the repo and setting the source to the docs-folder. Everything else should then work out from scratch. Probably linking the different pages needs to be taken care of.