Jonathan Roebuck

Great, thanks! > Maybe you can turn them in custom properties as workaround by adding one more leading dash? Ah I didn't think of that. I'll investigate this.

Hi @brandonkal I think I still need to use `stylelint-processor-styled-components` to parse css containing js variables and mixins though e.g. ```js const example = css` ${({ height }) => height...

I was thinking about an additional sentence in error pages for such situations that says something like "Please contact us with your browser, device, location etc so we can resolve...

Was chatting Josh there - there is bundle size improvements with this work. I think the most meaningful aspect of this work is the chance to improve routing in Simorgh....

@neildoughty you are correct - we are using font-display. Apologies, I'm playing catch-up on how we handle font loading. I'll change the above description of the issue because after doing...

@leoyli @chinesedfan thanks for responding to my issue. Leoyli's is a good solution but unfortunately it won't work in our specific case where we're also using the [csstree/stylelint-validator](https://github.com/csstree/stylelint-validator) plugin. This...

Hello. I like your suggestion @threepointone but I'm thinking it would make more sense to choose one rule and not allow a combination of both because I think this would...

@heath-freenome ah ok this makes sense. Thanks for mentioning how to work around it. > It may be that we can add a configuration option for our validator-ajv8 to filter...

> @jroebu14 using the idSchema, you can extract the path fairly simply by setting the [idSeparator](https://rjsf-team.github.io/react-jsonschema-form/docs/api-reference/form-props/#idseparator) prop on the Form to be . and then slicing out the root. @heath-freenome...

> Hi @jroebu14 and @backstage/maintainers would we like to proceed with this pull request, or will this component be added to Canon? @camilaibs we've decided to remove the Autcomplete component...