You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's show the theme's title and author in an obvious manner. This is a kick-off issue, and has an emphasis on initial architecture. As always in this milestone, this needs to be server-side-renderable from the start.
TODO:
Decide on data architecture — deferring until LRM, going to use 1.1 endpoint for now
Decide on whether we need layout-last routing — YES WE DO
Theme Details 1.2 REST endpoint, which gets its data from ES.
Reducer/selectors/fetchers for title and author
I think we could get some working skeleton quickest if we wrote a theme-details reducer and selectors that we connect to the exisiting 1.2 endpoint (which gives us name and author) for now, and re-wire to the new Details endpoint afterwards.
I think we could get some working skeleton quickest if we wrote a theme-details reducer and selectors that we connect to the exisiting 1.2 endpoint (which gives us name and author) for now, and re-wire to the new Details endpoint afterwards.
Yep, I can see us going that way initially. It'd be useful to have a think about the details API early on, so we don't keep adding fields to the list endpoint.
Let's show the theme's title and author in an obvious manner. This is a kick-off issue, and has an emphasis on initial architecture. As always in this milestone, this needs to be server-side-renderable from the start.
TODO:
Sub[Master]Bar
component CSS + markup Themes: Add themes detail page #3053Theme Details 1.2 REST endpoint, which gets its data from ES.UI:
The text was updated successfully, but these errors were encountered: