Feature Vaccine

[zenangst]

I have this idea of deprecating Vaccine as a framework and ship the implementation together with Injection. Vaccine will be an opt-in feature that will be enabled and disabled in the same way as you enable TDD.

If you have the implementation enabled and your class does not respond to injected, it will fall back to running Vaccine in order to rebuild the view controllers or views state.

I've tested this implementation on iOS and tvOS and it works as the Vaccine framework does.

The biggest change to the client-server implementation is that a message is sent to the client notifying it of the current vaccine preference setting.

[johnno1962]

I have to admit I’m not very keen on the change to not check whether a class implements the method “injected()” before it is add of the list of classes to be “swept”. The Sweep is the least reliable part of injection and it’s best not to attempt it if the user doesn’t opt in by implementing “injected()” on a class being injected. Otherwise the overall reliability of injection will be reduced.

[zenangst]

@johnno1962 I see your point, thanks for the feedback mate! Was a bit unsure how important the sweeper was, thanks for clearing that up. So I pushed a new commit that restores the sanity check for the sweeper and now the injected method will be invoked after vaccine is done recreating the objects state, but only if vaccine is enabled. So the default behavior for InjectionIII remains the same.

[johnno1962]

Do you need to check if the instance implements injected() now?? Just a thought.

[zenangst]

@johnno1962 nice catch, that extra responds(to:) has been removed :)

[johnno1962]

Looks good to me now. Don’t forget to squash 👍

[zenangst]

Squash is the new default!

[zenangst]

@johnno1962 I really appreciate you taking the time to review my PR's! ❤️