-
Notifications
You must be signed in to change notification settings - Fork 566
get tag combiner pages running in DCR #27953
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
Conversation
267e828 to
c31436b
Compare
|
Wow this is an awesome effort, thanks so much for getting this up and running @andrew-nowak! 👏 It would be great if we could add some basic docs around this, or at least make this article more discoverable. Tag combiner pages are a real power tool for devs and product-minded colleagues, useful for debugging and surfacing examples of specific content types. |
arelra
left a comment
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.
Great work thanks Andrew. Is there anything blocking this from release @SiAdcock ?
c31436b to
32f73e7
Compare
32f73e7 to
d3283b4
Compare
SiAdcock
left a comment
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.
This is awesome thanks @andrew-nowak 💎
|
Seen on ADMIN-PROD (merged by @andrew-nowak 12 minutes and 13 seconds ago)
|
|
Seen on FRONTS-PROD (merged by @andrew-nowak 12 minutes and 19 seconds ago)
|
What is the value of this and can you measure success?
What does this change?
A tag combiner page is just a tag page with a fancier query... right?
If we can render a tag page in DCR, then surely we can also render a tag combiner page!
(Yes we can, just the routes regex needs teaching that the
.jsonisn't part of the right tag, and a couple extra fields sent in the DCR model for the tag combiner page).Screenshots
Checklist
data/databasefiles generated by tests are committed with this PR (the tests will fail in CI if you've forgotten to do this)