[#7811] Allow InfoRequest to be categorised #8025
Merged
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
garethrees
reviewed
Nov 23, 2023
gbp
force-pushed
the
7811-categorisable
branch
4 times, most recently
from
1afdf3b to
a06e473
Compare
gbp
force-pushed
the
7811-categorisable
branch
from
a06e473 to
eefcba1
Compare
Update to handle any model which include the Categorisable concern.
Allow categoies to be created to organise `InfoRequest` with given `category_tag`. Fixes #7811
gbp
force-pushed
the
7811-categorisable
branch
from
eefcba1 to
3f6a668
Compare
|
Reviewed and approved on a call together. |
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.
Relevant issue(s)
Depends on #8023
Fixes #7811
What does this do?
Add
categorisableconcern and adds this toInfoRequestWhy was this needed?
So we can so groups of requests on topic pages.
Screenshots