You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keeping app config entries clean and up to date is difficult - we should make an extra effort to help keep our own Hoist-installed xhXXX app configs current.
I propose a careful review of our codebase across hoist-core and hoist-react to inventory every config we read so we can:
Ensure that all current configs are created with reasonable defaults in hoist-core Bootstrap
Provide an in-code list of these same configs
We could then leverage this list to alert admins to configs found in an app's DB that are no longer supported by the toolkit. Possible approaches there could be:
Query configs on app startup and log a warning for any unexpected DB configs
Could be exposed as a reusable method if apps wanted to impl the same pattern
More complex but potentially more actionable option would be to surface this info in hoist-react console - e.g. have that module get the list of supported configs and have some extra handling to flag them in the grid or toolbar.
The text was updated successfully, but these errors were encountered:
Keeping app config entries clean and up to date is difficult - we should make an extra effort to help keep our own Hoist-installed
xhXXX
app configs current.I propose a careful review of our codebase across hoist-core and hoist-react to inventory every config we read so we can:
We could then leverage this list to alert admins to configs found in an app's DB that are no longer supported by the toolkit. Possible approaches there could be:
The text was updated successfully, but these errors were encountered: