Fixed dependency on the method formViewController(), subclassing of FormViewController not necessary anymore. #832
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 7 commits
December 8, 2016 14:23
- Extended FormViewControllerProtocol - Added Example Custom FormViewController as ChildViewController - Added some guards for optionals that caused crashes with custom FormViewControllers
# Conflicts: # Source/Core/BaseRow.swift
|
Hello, any update about this PR (or this funcionality). Have to extending FormViewController is very limiting in many applications. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In the Project Readme I read
but it didn't work for me. The cause was the dependency on the FormViewController class (or subclass) in the source, now it's fixed.