guardian / guardian/concierge-graphql
Respect `takenDown` and `embargo` flags
Open
- Dominant language
- Scala
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
These definitely exist on atoms and may exist elsewhere
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating how atoms are exposed through the GraphQL Content API and where the `takenDown` and `embargo` flags are represented. Determine the intended behavior for flagged atoms and whether the flags apply elsewhere; the work is done when the relevant responses consistently respect that behavior and the repository's checks cover it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, scala
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100