Renamed InlineFormSet to InlineFormSetFactory and other renames #167
Conversation
This file contains 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
1. Renamed BaseFormSetMixin to BaseFormSetFactory. 2. Renamed BaseInlineFormSetMixin to BaseInlineFormSetFactory. 3. Renamed InlineFormSet to InlineFormSetFactory. 4. Renamed BaseGenericInlineFormSetMixin to BaseGenericInlineFormSetFactory. 5. Renamed GenericInlineFormSet to GenericInlineFormSetFactory. 6. Updated docs and tests. 7. Updated changelog.
Codecov Report
@@ Coverage Diff @@
## master #167 +/- ##
==========================================
- Coverage 52.79% 50.98% -1.82%
==========================================
Files 6 6
Lines 483 508 +25
Branches 56 56
==========================================
+ Hits 255 259 +4
- Misses 212 233 +21
Partials 16 16
Continue to review full report at Codecov.
|
|
LGTM thanks! |
|
Great :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Let me know if the way I've handled the deprecation warnings is OK; I assumed just checking on
__init__would be sufficient.#165.