Steve Sims

This work is now mostly complete. Remaining items are components that require some further thought and/or refactoring, mostly because they don't currently match the way that govuk-frontend works. For example:...

the few components that remain un-ticked do still need a bit of attention/consideration. `ErrorSummary` for example does have it's own custom font adjustments, and thus isn't using the standardised typography...

in the case of conditionally revealed content, i would expect govuk-react to provide the container, as per `.govuk-radios__conditional` and `.govuk-checkboxes__conditional` but not to provide any logic for revealing that content....

I'd expect these to be implemented as `Radio.Conditional`, `Checkbox.Conditional` and `Radio.Divider`

The slight complication here is that the way we handle multiple checkboxes and radio buttons in govuk-react differs from how things are put together in govuk-frontend. We have components for...

Unfortunately not. I moved on from the project where I'd been working on govuk-react, and rarely get a chance to put in much work on it these days. PRs are...

The `deprecate` HOC now provides a mechanism for marking whole components as deprecated. At present there is no generic "deprecate a prop" mechanism - instead that is being done on...

Further to this, the style of the `Input` component does not match govuk-frontend - it is instead based off an older govuk design pattern. The 50% width media query is...

unfortunately the partial storybook update that prompted this didn't cause the storyshots visual regression coverage test to fail the storybook however was non-functional - it compiles, and will load in...

This style of component also appears in the Home Office Design System as Alerts. See: https://home-office-digital-patterns.herokuapp.com/components/alerts NB we have a draft of this, but it has not yet been imported.