Optionally enable/disable features on contact types #227
+121
−44
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
paulpascal
requested changes
Nov 20, 2024
kennsippell
requested changes
Nov 26, 2024
|
Have you tried this change on production data like the Nairobi instance. It will download and cache every household... Does it just explode? |
|
I tried it on production and the request never completed so we can't actually search for households this way. Not sure if using the |
Open
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.
This PR introduces a way to explicitly enable/disable the main 3 features of this app i.e creating places, replacing contacts and moving places. This came from this request where users need to be allowed to move households but not create/replace. All features are enabled by default but this can be configured using the
feature_flagsfield.