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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor AdminSetCreateService to work with both AdminSet and AdministrativeSet #5224
Refactor AdminSetCreateService to work with both AdminSet and AdministrativeSet #5224
Changes from 10 commits
e4bd0fa
817a495
6a18f5d
104466b
563ba63
7922158
0a98093
9ea09ba
094bb3c
3a000f3
485d369
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think it would be nice to rebase these changes on #5213. some of the changes overlap, but i think that does a more complete job of fixing up the stubs, indirection, and multi-expectations in these specs.
i'd be willing to take on that rebase today if that PR could be reviewed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am open to even more refactoring of the tests. It would be easier to review another round of refactoring if this PR were merged with the tests as is and follow that with an update to #5213 or a new PR that makes additional changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think reworking #5213 in light of these changes would amount to doing the work in it over again. on the other hand, the substantive changes in this PR are in another file, and it will likely continue to pass, or possibly require minor adjustments, if rebased on #5213.
i feel willing to do the work involved in latter, but not the former.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My preference to overlay the #5213 changes is that the specs are rearranged in this PR to closer match that actual methods. The primary tests are only run for
#create!
since it is the only method that does any work beyond passing through data related to the new admin set. Other methods, including a few new methods, are only tested to ensure they pass through expected data and return expected values.I am taking on the work to overlay #5213 over this PR in PR #5227.