Adding sensitive content warning/filter to detail and search#571
Adding sensitive content warning/filter to detail and search#571ajolipa wants to merge 1 commit into
Conversation
✅ Deploy Preview for padp-staging ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for pss-scavenger-hunt ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for gbof-c19nyc-staging ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for juel-staging ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for juel-ancestry ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for universities-studying-slavery ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for juel-life ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for registro-project ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for libertos ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for gamepossible ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
camdendotlol
left a comment
There was a problem hiding this comment.
Looks good, just a couple small changes.
| const config = useSearchConfig(); | ||
|
|
||
|
|
||
| if (!(config.type === 'image')) { |
There was a problem hiding this comment.
Let's do config.type !== 'image' for clarity
|
|
||
| const service = ServiceFactory.getService(model); | ||
| const manifests = await service.getRelatedManifests(uuid); | ||
| const { mediaContents } = await service.getRelatedMedia(uuid); |
There was a problem hiding this comment.
The content warning field should be included in the manifests, so it would be better for load times to get it from there instead of adding a second fetch request.
See
for an example that can probably be factored out into a helper function and shared between this component and that one.
In this PR
This PR does two things:
content_warning: true;Notes
content_warningfield work better on front end core-data-cloud#557