maykinmedia/admin-ui

Our Maykin toolkit with reusable components for admin apps

Maykin UI

A reusable component library developed by Maykin Media.

DEVELOPMENT NOTICE

This libray is in active development.

admin-ui's Issues

Investigate further filterTransform improvements

#83 (review)

• Optionally add per field filterTransform (without causing conflicts)
• Improve (Story) documentation

Implement help text

Implement dynamic form schema

The goal is that we can do things like specifying what fields should be renderred when a specific value in the form is selected (for example a specific radio field)

Fix build warnings

Currently, when building open-archiefbeheer frontend, we get the following warnings:

Module not found: Error: Can't resolve 'react-intl' in '/home/silvia/repositories/open-archiefbeheer/frontend/node_modules/@maykin-ui/admin-ui/dist/esm/lib/i18n'

Module not found: Error: Can't resolve './messages/nl.json' in '/home/silvia/repositories/open-archiefbeheer/frontend/node_modules/@maykin-ui/admin-ui/dist/esm/lib/i18n'

Module not found: Error: Can't resolve './messages/en.json' in '/home/silvia/repositories/open-archiefbeheer/frontend/node_modules/@maykin-ui/admin-ui/dist/esm/lib/i18n'

It would be good to fix these warnings

Implement Radio(group)

Currently the radio(group) isn't implemented.

General improvements [Frontend]

Things that were noticed while working on maykinmedia/open-archiefbeheer#54

• The component AttributeTable does not wrap on mobile view
• In the DataGrid component, if there are few rows and the paginator is used, the paginator is shown under the last row of the table. It would be nice to be able to show it at the bottom of the page like in this design
  
• When the component DataGrid is loading, the spinner is shown on the paginator (very small). I hadn't noticed it at all in the beginning, so I think the 'loading' state needs to be clearer. It should also not be possible to select/deselect items while data is being fetched.
• In the DataGrid component with filters, for every keystroke a request is sent to the backend. This should probably be debounced.