Add additional content and followable checks to home page artwork modules
See original GitHub issueIdeally the response would provide some sort of context for these cases so they don’t have to be individually checked for by the client:
So fields like has_additional_content
and followable
would be nice. Maybe is_followed_by_user
too.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Add items - Google Arts & Culture Platform Help
Upload content. In the Items page icon Items manager, click the arrow next to Add new items select Simple import. Choose from one...
Read more >AP Art History Course and Exam Description - College Board
Through more than 30 courses, each culminating in a rigorous exam, AP provides willing and academically prepared students with the opportunity to earn...
Read more >29 Best WordPress Themes for Artists - WPBeginner
Check out our pick of the best WordPress themes for artists. ... You can add categories, custom widgets, and more on the homepage....
Read more >How do I use the Modules Index Page? - TeamDynamix
As an instructor, you can add modules, add items to a module, and manage module settings. You can also reorder all modules and...
Read more >Chapter 5 Arena Basics - Semantic Scholar
Process Module (Cont.) Page 10. Altiok / Melamed Simulation Modeling and Analysis with Arena. Chapter 5. 10.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sarahscott for the related content, it might be useful to look at how we handle this on Force.
For instance, an individual module: https://github.com/artsy/force/blob/master/apps/home_2/queries/module.coffee
context
is a GraphQLUnion type that is switched depending on the type of module returned. We use these contexts switches to get additional info on the module (e.g. Auction metadata, Related artist “based on”, etc).For the Related Artists example: https://github.com/artsy/force/blob/master/apps/home_2/components/related_artists_context/query.coffee
Context definitions are here: https://github.com/artsy/metaphysics/blob/master/schema/home/context.js
@sarahscott @broskoski what are your thoughts on this nowadays?