-
Notifications
You must be signed in to change notification settings - Fork 17
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
Use GraphQL for rendering Role page #3845
base: main
Are you sure you want to change the base?
Commits on Nov 13, 2024
-
Swap instance variable for local
The instance variable isn't being used anywhere Co-authored-by: Ynda <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 1900795 - Browse repository at this point
Copy the full SHA 1900795View commit details -
Move Role's presentation into a presenter
Co-authored-by: Ynda <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 325b099 - Browse repository at this point
Copy the full SHA 325b099View commit details -
Introduce Role page feature spec
Exercising the role page with a few alternate content item configurations, hopefully triggering all combinations of partials to be rendered Co-authored-by: Ynda <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for d601808 - Browse repository at this point
Copy the full SHA d601808View commit details -
Define sub-presenters for Role's links
Negating the use of hashes in the roles views. We've taken this opportunity to flatten some of the data that was in those hashes -- see the removal of the "details" layers. We're working towards introducing Publishing API's GraphQL endpoint as an alternate source for Role data. If the current approach is preferred, we'd be happy to build hashes from that new data, and to have those hashes reflect internal details specific to the ContentItem data. But since it didn't appear difficult to change, we thought we'd have a go at making something more neutral. --- We're not sure yet about the use of Data objects here. It seemed like a nice idea to begin with but after it was finished and working we weren't completely convinced that it wasn't a bit "too smart". Co-authored-by: Ynda <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for db64da0 - Browse repository at this point
Copy the full SHA db64da0View commit details -
We're trialling Publishing API's GraphQL endpoint as a source for Role data like we did recently for the World Index Co-authored-by: Ynda <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for e796d5c - Browse repository at this point
Copy the full SHA e796d5cView commit details -
Add prime-minister role test fixture
This fixture reflects how Publishing API's GraphQL endpoint represents the prime-minister role Co-authored-by: Ynda <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for ebfb868 - Browse repository at this point
Copy the full SHA ebfb868View commit details -
Introduce a Graphql-specific Role model
Co-authored-by: Ynda <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 4f05e86 - Browse repository at this point
Copy the full SHA 4f05e86View commit details -
Introduce a GraphQL-specific Role presenter
Co-authored-by: Ynda <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 1d843cc - Browse repository at this point
Copy the full SHA 1d843ccView commit details -
Check for GraphQL feature flag in Roles controller
Co-authored-by: Ynda <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 46cc139 - Browse repository at this point
Copy the full SHA 46cc139View commit details