-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat/module app/appsettings/getter #2577
Conversation
🦋 Changeset detectedLatest commit: d856c4f The changes in this PR will be included in the next version bump. This PR includes changesets to release 11 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
0cfc99e
to
25c7ee4
Compare
ce2694c
to
436ce93
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should have a quick squad code review on this feature, setting up a meeting
db0c0e4
to
bd631bf
Compare
bd631bf
to
a08dd60
Compare
… client provider and flows
* fix(cli): vite-proxy for persons/me/settings with own use proxy path * fix(app-settings): improvements to flows * fix(app-module): faiilover when meta.id is not set. vite proxy handles manifest only * feat(cli): add appSettingsPlugin to handle app settings requests * feat(app): add updateSetting and updateSettingAsync methods for app settings management * fix(react-app): fix build of app settings - Add README.md to settings directory - changed functionality of `useAppSetting` from allowing dot path to only allowing root property name - removed dot-path.ts * feat(react-app): add initial setup for app-react-settings cookbook with configuration and main app component * chore(dependencies): update devDependencies for app-react-settings cookbook * Empty-Commit * refactor(app): simplify state selection for observables in App class * fix(app): improve action filtering for updateSettings in App class * fix(app): enhance AppClient to utilize IHttpClient for updating app settings `Query` does not support update actions, since the query method only execute a method, so the update must done in a separate action which mutates the query on update. * fix(app): update appSettingsPlugin to directly assign parsed request body for PUT method align the plugin with PUT, not PATCH * fix(app): update settings handling and improve action structure in AppClient * fix(app): enhance useAppSetting and useAppSettings hooks to support status handling and improve error management * fix(app): enhance useAppSetting and useAppSettings hooks to support callback functions for setting updates and improve error handling * fix(app): enhance App component to support new 'fancy' setting and loading states for theme and size updates * fix(deps): add fast-deep-equal dependency at version 3.1.3 in pnpm-lock.yaml * docs(settings): add section for Portal Settings in README.md * feat(docs): add documentation for app settings * docs(settings): update README.md with notes on global state handling and UI best practices for settings updates --------- Co-authored-by: Øyvind Eikeland <oyvind@eikeland.me>
d856c4f
to
3fdaa1f
Compare
Changes:
AppClient.ts
updateAppSettings
method to set app settings by appKey.#setSettings
query in the constructor.AppModuleProvider.ts
updateAppSettings
method to update app settings.App.ts
updateSettings
andupdateSettingsAsync
methods to set app settings.actions.ts
updateSettings
async action for updating settings.create-reducer.ts
updateSettings.success
to update state settings.create-state.ts
handleUpdateSettings
flow to handle updating settings.events.ts
onAppSettingsUpdate
,onAppSettingsUpdated
, andonAppSettingsUpdateFailure
.flows.ts
handleUpdateSettings
flow to handle the set settings action.package.json
settings
entry to exports and types.index.ts
useAppSettings
.useAppSettings.ts
Devops: AB#56190