What problem does this feature solve?

I want to provide additional properties to a menu for example to make it better testable. This works but TS is reporting an error as the attribute 'data-test' does not exit in type ItemType.

const items: Array<ItemType> = [
    {
      key: 'exercises',
      // @ts-ignore
      'data-test': 'exercises',
      icon: <Fa icon={faTasks} fixed

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

When I augment IconButton with new colors:

declare module "@mui/material/IconButton" {
  interface IconButtonPropsColorOverrides {
    textPrimary: true;
    textSecondary: true;
  }
}

and then try to use these colors:

<

Describe the bug
In Firefox, the zoom feature uses transform styles (see storybookjs/storybook#12845) - unfortunately this breaks positioning on elements that require position: fixed when in the "Docs" view.

Normally a position: fixed element's position would correspond to the viewport but in Firefox it corresponds to the element with the transform style.

<Select /> and <DatePicker /> don't offer the option of accessing name, id and other props once the onChange handler triggers. An event object with this information is accessible in the onChange handler for <Input />.

Feature description

Provide access to these variables for Select and DatePicker. It is needed when the component is being passed handler functions from an

https://github.com/kgrzybek/modular-monolith-with-ddd/blob/54d209639e501301e879aa0d0a84c9ea49e4689e/src/Modules/Meetings/Domain/Meetings/Rules/MeetingAttendeesLimitMustBeGreaterThanGuestsLimitRule.cs#L1-L21

I believe the comparison operator used in the IsBroken method is wrong because the rule is checking that meeting attendees limit must be greater than guests limit.

🐛 Bug Report

In my next.js where I'm adding in React Spectrum, I placed the <Provider/> in my /pages/_app.tsx:

<SSRProvider>
  <Provider>
    {/* ... */}
  </Provider>
</SSRProvider>

Describe the bug

We (the Login.gov team) have implemented the checkbox and radio buttons with optional text to the Login Design System. The Login design system is built on top of USWDS.

When testing a form using a screen reader (specifically in Chrome using JAWS and NVDA), I found that when a user reads or scans the entire page, content within the label is announced twice. For example, in

One of the consumers of our system uses curly braces for content replacement in strings.

Due to the way that SD currently uses curly braces in the build process there is no way I can have a string that includes the braces for consumption.

I have tried a number of ways to escape the braces with no luck

Other languages and templating systems seem to use the concept of using double curly b