fixed isset problem with parent objects, used magic method __isset() #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using the service provider to automagically create Presenter instances of objects, I found there was a problem with using Form::model(), as it uses isset() to check values on the bound model. Since Presenter is just a wrapper, the values are not set. By implementing the __isset() it keeps the Form::model() working as expected. Hopefully this is an acceptable addition.