Merged
Conversation
Contributor
Author
|
Test Failure: Looks like error in difference in Plan content. No something I changed. Any ideas on fix |
Contributor
|
My guess would be that the plan used in that test has an issue with the role(s) used. The test itself likely needs to be updated rather than it being an issue with your changes |
Changes:
- Replaced .where(Role.creator_condition) with .where(roles: { active: true })
in model Plan search scope.
b3821d9 to
de99557
Compare
portagenetwork
pushed a commit
to portagenetwork/roadmap
that referenced
this pull request
Feb 24, 2022
…hboard_and_other_display_of_plans Issue #496 - Plan search issues.
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
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.
Fixes #496 .
The specification for Plans search and display was cited by @mariapraetzellis in comment
#3000 (comment)
Further comments by @raycarrick-ed and @briri are linked here:
#3000 (comment)
#3000 (comment)
Changes proposed in this PR: