DEV: Add topic custom field for nesting#35
Merged
markvanlan merged 2 commits intomainfrom Mar 25, 2026
Merged
Conversation
xfalcox
approved these changes
Mar 24, 2026
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
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.
Instead of relying on category setting to know if we should route to nested or flat view, use property directly on the topic model. This make routing much more simple, and allows us to enable nesting on specific topics without having to enable for a whole category.
When clicking a notification link and nesting is installed we have to do a check for the topic. Instead of hitting the regular topic endpoint this adds a very lightweight endpoint to check.
This still isn't ideal still but.. here we are at the moment..