UILD-696: Add default and settings selector components to manage profile settings view#299
Merged
zepheiryan merged 13 commits intomasterfrom Jan 26, 2026
Merged
UILD-696: Add default and settings selector components to manage profile settings view#299zepheiryan merged 13 commits intomasterfrom
zepheiryan merged 13 commits intomasterfrom
Conversation
… API, add loading indicator
… and functionality
SKarolFolio
approved these changes
Jan 26, 2026
pkjacob
approved these changes
Jan 26, 2026
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
https://folio-org.atlassian.net/browse/UILD-696
Make components for profile as resource type default and active settings, tied to API values.
When settings are active as read from the API (radio buttons):
When profile is default for the resource type as read from the API (checkbox):
(In order to work in standalone mode with a FOLIO user, I locally patched
'x-okapi-user-id'into the headers forfetchProfileSettingsandfetchProfileSettingsinprofiles.api.tsand added database values to match in the corresponding tables.)