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
For schemas (e.g. cms) we have some of the "config" properties in the root of the schema (e.g. fullname, version, experiment) instead of having them inside the config property, which only contains. Those properties are saved in the redux state in schemaWizard.config, so it would make more sense if all of them were grouped (also because most of them come from the schema config) and would be less error prone. Also, config already exists and notifications are already saved inside of it, so the ideal result would be:
This would be easy to change in the UI, but it requires changing the backend (validation, etc) as well as updating the existing schemas.
With this change, instead of
const{ deposit_schema, deposit_options, ...configs}=data;// We don't necessarily need to store every prop in ...configs in the redux state// but else we'd need to filter manually here (and not only here) which is not idealstore.dispatch(updateSchemaConfig(configs));
we could do
store.dispatch(updateSchemaConfig(data.config));
The text was updated successfully, but these errors were encountered:
For schemas (e.g. cms) we have some of the "config" properties in the root of the schema (e.g. fullname, version, experiment) instead of having them inside the
config
property, which only contains. Those properties are saved in the redux state in schemaWizard.config, so it would make more sense if all of them were grouped (also because most of them come from the schema config) and would be less error prone. Also,config
already exists and notifications are already saved inside of it, so the ideal result would be:whereas now we have:
This would be easy to change in the UI, but it requires changing the backend (validation, etc) as well as updating the existing schemas.
With this change, instead of
we could do
The text was updated successfully, but these errors were encountered: