v4.0.0

4.0.0 (2021-04-13)

Bug Fixes

• add a param to ignore old params in redirect urls (5b0deb7)
• call new simplified create() method on save (afb5883)
• fix an issue where mixed type would add another nesting layer (0e19886)
• Revert yarn.lock (a4b69d6)
• temporarily set i18next to fixed v19.8.7 (379e502)
• use design system >v1.7.3 to fix datepicker input issue (55d7699)
• use the latest @admin-bro/design-system (2e79e0a)

Features

• add drag and drop to allow to reorder array elements (d1c1213)
• Allow sidebar override (d670a52)
• move accessibility check to after before hook is called (58c809a)
• store previous page url in location state when navigating (c73d1d0)

BREAKING CHANGES

• This is to force major version release due to one of the changes in earlier commits.
  #765 fixed a bug where 'mixed' (JSON/JSON Array) properties would be nested under it's own name in the database.
  It also resulted in the property being displayed incorrectly in 'show' action view later.
  If you used 'mixed' type previously, you might need to migrate your database data to work with the improved syntax.
  Example resource config:

properties: {
  additional_data: { type: 'mixed' },
  'additional_data.label': { type: 'string' },
  'additional_data.value': { type: 'string' },
}

If the above config results in your data being saved as:

{ "additional_data": { "label": "test", "value": "test" } }

instead of

{ "label": "test", "value": "test" }

in your database under 'additional_data' column, an example migration for PostgreSQL would be:

UPDATE my_table_name
SET additional_data = jsonb_extract_path(additional_data, 'additional_data');