Allow hiding indicator list page insights with page settings #170
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
woodwoerk
reviewed
Sep 26, 2023
| @@ -210,9 +210,10 @@ const getFirstUsableCategoryType = (categoryTypes, indicators) => | |||
| interface Props { | |||
| title: string; | |||
| leadContent: IndicatorListPage['leadContent']; | |||
| displayInsights: boolean; | |||
There was a problem hiding this comment.
According to the generated types this could be undefined. Should we make this optional and default to true for backwards compatibility?
There was a problem hiding this comment.
Hmm. That is a problem in the type generation since in the Django backend it cannot be null/undefined and in the GraphQL schema it's a Boolean. But still, I can make the change.
woodwoerk
approved these changes
Sep 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.