Set up FLEx-lite view permissions and API features #861
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
UI unit Tests11 tests 11 ✅ 0s ⏱️ Results for commit 9a184af. ♻️ This comment has been updated with latest results. |
hahn-kev
approved these changes
Jun 5, 2024
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.
Resolves #862
This PR adds the concepts of:
to FLEx-lite and the 3 APIs we use.
So, now the UI only displays supported features (with the ability to toggle them in dev mode)
It also replaces the FLEx-lite header with the name of the project, so that we don't have to think about branding yet.
I wasn't sure where to best introduce the API features, so I'm intrested to hear if there are other ideas.