GitHub repository: patternfly/patternfly-react

Issues:
issue_10111: state: open
title: Create BasicSelect widget & example
user: kmcfaul
issue_10110: state: open
title: feat(templates): add templates package
body: <!-- What changes are being made? Please link the issue being addressed. -->
**What**: Closes #10109 and #10111

Adds the new package to repo with basic template, and sets up documentation.

https://github.com/patternfly/patternfly-org/pull/3902 needs to be merged before docs build will succeed. But first I want to confirm the starting version of `1.0.0-alpha.0`. Are we good starting from `1` or do we want to start from `5` to match other PF packages?

What does everyone think about `react-templates` as the package name as well?
user: kmcfaul
issue_10109: state: open
title: Create new package `patternfly-widgets` in `patternfly-react`
user: kmcfaul
issue_10108: state: open
title: Bug - [Toolbar] - [missing OUIA for filter toggle]
body: **Describe the problem**
OUIA is a great selector for writing tests.
Toolbar filters are missing "good" OUIA selectors so we can target them.

https://github.com/RedHatInsights/frontend-components/pull/1972
Here's an example of what Georgy did for the primary toolbar component in frontend components.
I think it would be great to copy that from frontend components and bring it to the Patternfly

**Expected behavior**
We have the same OUIA as in frontend components.

**Is this issue blocking you?**
No, but its QOL improvement


**What is your product and what release date are you targeting?**
console.redhat.com
user: Fewwy
issue_10107: state: open
title: feat(Login): use children for loginmainfooterlinksitem
body: <!-- What changes are being made? Please link the issue being addressed. -->
**What**: Closes #10100

Removes inner structure of `LoginMainFooterLinksItem` and updates examples to pass buttons directly. 
user: kmcfaul
issue_10106: state: open
title: Bug - ClipboardCopy - preview for expansion variant does not stringify properly for all allowed types
body: **Describe the problem**
Follow up to #9711 as the previous fix had to be reverted because it was an unintentional breaking change.

The new approach should solve the issue **without** limiting the allowed types of ClipboardCopy to only a string.

A potential solution is that:

- the expansion preview (or maybe expansion variant?) should not allow react node child
- documentation is improved to let users know that if they do indeed pass something other than string as the child, they will need to override onCopy


**Expected behavior**
Expansion variants do not provide an improperly stringified preview

**Screenshots**
![image](https://github.com/patternfly/patternfly-react/assets/7115053/75492ec7-9104-42fc-95c4-aa9e9652e693)

CC @gitdallas 
user: wise-king-sullyman
issue_10105: state: open
title: Password strength + generator demos docs location
body: These two demos are currently under "Components" but should probably be moved under "Patterns" with the other aggregate demos.
user: kmcfaul
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_10104: state: open
title: Bug - [Card] - `isSelectable` not working in webkit 122
body: **Describe the problem**
`Card` component are no longer clickable / selectable in chrome / webkit 122.

**How do you reproduce the problem?**
Use the [Card Single Selectable](https://www.patternfly.org/components/card#single-selectable) example (or any other example with clickable cards) on the patternfly website. With the latest chrome or edge (v 122), the card is no longer selectable. You must use the radio button in the top right corner. 

Visit the same page with Firefox and it works.

**Expected behavior**
Expected card to be selectable.

**Is this issue blocking you?**
Yes.

**What is your environment?**
 - OS: mac intel
 - Browser: Chrome, edge
 - Version: 122

**What is your product and what release date are you targeting?**
RHOAI

**Any other information?**

user: christianvogt
issue_10101: state: open
title: feat(TreeView): removed selectable modifier for penta
body: <!-- What changes are being made? Please link the issue being addressed. -->
**What**: Closes #10010 

<!-- Are there any upstream issues or separate issues you need to reference? -->
**Additional issues**:

user: wise-king-sullyman
issue_10100: state: open
title: Login - remove link component in LoginMainFooterLinksItem
body: Use children directly instead & update examples.
user: kmcfaul
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_10097: state: open
title: feat(MenuToggle): consumed Penta updates
body: <!-- What changes are being made? Please link the issue being addressed. -->
**What**: Closes #9986
[Codemod](https://github.com/patternfly/pf-codemods/issues/584)

This also bumps the Core versions

<!-- Are there any upstream issues or separate issues you need to reference? -->
**Additional issues**:

user: thatblindgeye
issue_10096: state: open
title: V6 - Drag drop - Deprecate drag drop
body: **Describe the enhancement or change**
A clear and concise description of the request. What is the expected outcome?
Deprecate drag drop in v6 branch.  Move it to deprecated directory.

user: tlabaj
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_10095: state: open
title: Drag drop -"soft" deprecate
body: **Describe the enhancement or change**
A clear and concise description of the request. What is the expected outcome?

add `isDeprecated` tab to MD file for drag drop.  Do not move code to deprecated directory.  We want to encourage consumers to use new solution, but we do not want to break them
user: tlabaj
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_10094: state: open
title: Chore - Chart - Clean up tooltip examples
body: I discovered a couple issues with the chart examples, which I'd like to clean up. 

Tooltip embedded HTML: https://www.patternfly.org/charts/tooltips/#embedded-html

- The offset and flyout component are not necessary here
- `ChartPoint` should be encapsulated wit a `rect` tag
- `flyout` property should be `flyoutComponent`

Boxplot embedded legend: https://www.patternfly.org/charts/box-plot-chart#embedded-legend

- `boxPlotData` property does not exist
- This can be modified to better show all boxplot properties by wrapping lines in the legend tooltip

Closes https://github.com/patternfly/patternfly-react/issues/10093


user: dlabrecq
issue_10093: state: open
title: Chore - Chart - Clean up tooltip examples
body: I discovered a couple issues with the chart examples, which I'd like to clean up. 

Tooltip embedded HTML: https://www.patternfly.org/charts/tooltips/#embedded-html

- The offset and flyout component are not necessary here
- `ChartPoint` should be encapsulated wit a `rect` tag
- `flyout` property should be flyoutComponent

Boxplot embedded legend: https://www.patternfly.org/charts/box-plot-chart#embedded-legend

- `boxPlotData` property does not exist
- This can be modified to better show all box plot properties by wrapping lines in the legend tooltip
user: dlabrecq
issue_10092: state: open
title: Bug - [UploadFile] - [Can't upload system files]
body: **Describe the problem**
Trying to upload a system file (like ssh pub key) is not allowed anymore.
This is a regression as PF4 did allow this.

**How do you reproduce the problem?**
Go to [PF docs > FileUpload](https://www.patternfly.org/components/file-upload/simple-file-upload/) and try to upload an SSH public key, A window alert will pop from the browser and prevant this action

**Expected behavior**
The upload should occur regularly

**Is this issue blocking you?**
I couldn't find any workaround

**Screenshots**

https://github.com/patternfly/patternfly-react/assets/67270715/b160a910-7bb7-4303-adf0-9c391c3f202d



**What is your environment?**
 - OS: [e.g. iOS]
 - Browser Chrome (on firefox it works fine)
 - Version 5.1.1

**What is your product and what release date are you targeting?**

**Any other information?**

user: avivtur
issue_10091: state: open
title: DualListSelector - apply penta updates to next component
body: Ensure penta styling updates also gets applied to the next version of DLS.

user: kmcfaul
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_10090: state: open
title: Bug - DragDropSort - dragged element transform inaccruate when DragDropSort is in DrawerPanelContent
body: **Describe the problem**

I combined the examples for Drag and Drop and Drawer with very few modifications:

- https://www.patternfly.org/components/drag-and-drop/react-next#basic-drag-and-drop-sorting-with-drag-button
- https://www.patternfly.org/components/drawer#inline-panel-at-start

```typescript
import React from 'react';
import {
  Drawer,
  DrawerPanelContent,
  DrawerContent,
  DrawerContentBody,
  DrawerHead,
  DrawerActions,
  DrawerCloseButton,
  Button
} from '@patternfly/react-core';
import {DragDropSort, DraggableObject} from "@patternfly/react-drag-drop";

export const DrawerInlinePanelStart: React.FunctionComponent = () => {
  const [isExpanded, setIsExpanded] = React.useState(true);
  const drawerRef = React.useRef<HTMLDivElement>();

  const onExpand = () => {
    drawerRef.current && drawerRef.current.focus();
  };

  const onClick = () => {
    setIsExpanded(!isExpanded);
  };

  const onCloseClick = () => {
    setIsExpanded(false);
  };

  const [items, setItems] = React.useState<DraggableObject[]>([
    { id: 'with-button-1', content: 'one' },
    { id: 'with-button-2', content: 'two' },
    { id: 'with-button-3', content: 'three' },
    { id: 'with-button-4', content: 'four' },
    { id: 'with-button-5', content: 'five' },
    { id: 'with-button-6', content: 'six' },
    { id: 'with-button-7', content: 'seven' },
    { id: 'with-button-8', content: 'eight' },
    { id: 'with-button-9', content: 'nine' },
    { id: 'with-button-10', content: 'ten' },
    { id: 'with-button-11', content: 'eleven' },
    { id: 'with-button-12', content: 'twelve' },
    { id: 'with-button-13', content: 'thirteen' },
    { id: 'with-button-14', content: 'fourteen' },
    { id: 'with-button-15', content: 'fifteen' },
    { id: 'with-button-16', content: 'sixteen' },
    { id: 'with-button-17', content: 'seventeen' },
    { id: 'with-button-18', content: 'eighteen' },
    { id: 'with-button-19', content: 'nineteen' },
    { id: 'with-button-20', content: 'twenty' },
  ]);

  const panelContent = (
    <DrawerPanelContent>
      <DrawerHead>
        <span tabIndex={isExpanded ? 0 : -1} ref={drawerRef}>
          drawer content
        </span>
        <DrawerActions>
          <DrawerCloseButton onClick={onCloseClick} />
        </DrawerActions>
      </DrawerHead>
      <DragDropSort
        items={items}
        variant="defaultWithHandle"
        onDrop={(_, newItems) => {
          setItems(newItems);
        }}
      />
    </DrawerPanelContent>
  );

  const drawerContent =
    'Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat,nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate.';

  return (
    <React.Fragment>
      <Button aria-expanded={isExpanded} onClick={onClick}>
        Toggle drawer
      </Button>
      <Drawer isExpanded={isExpanded} isInline position="start" onExpand={onExpand}>
        <DrawerContent panelContent={panelContent}>
          <DrawerContentBody>{drawerContent}</DrawerContentBody>
        </DrawerContent>
      </Drawer>
    </React.Fragment>
  );
};


export default DrawerInlinePanelStart;

```


**How do you reproduce the problem?**

https://github.com/jennydaman/patternfly-react-drag-drop-in-drawer

**Expected behavior**

Dragged element stays under the mouse.

**Is this issue blocking you?**

It is blocking us from using the Drag and Drop feature, but I can choose to use a different UX instead.

**Screenshots**

https://github.com/patternfly/patternfly-react/assets/20404439/d842c246-0cde-4b05-bbe1-0a21c775bf0b


**What is your environment?**
 - OS: Linux
 - Browser Chromium, Firefox
 - Version 5.2.0

user: jennydaman
issue_10089: state: open
title: feat(Menu): consumed Penta updates
body: <!-- What changes are being made? Please link the issue being addressed. -->
**What**: Closes #9985, closes #10076

There's some styling issues on hover for the menu item action. This is because in Core there's no `pf-v5-c-menu__item-action-icon` wrapper around the icon, while in React there is.

<!-- Are there any upstream issues or separate issues you need to reference? -->
**Additional issues**:

user: thatblindgeye
issue_10088: state: open
title: Expandable card/Expandable section consistency
body: When comparing the Expandable card component to the Expandable section I noticed that the expand toggle icon changes color (black/grey) on focus for the card and not for the expandable section
https://www.patternfly.org/components/card#expandable-cards
https://www.patternfly.org/components/expandable-section
Not sure if that's intentional. It might be worth making the experience consistent.

**Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?**
PatternFly React component groups extension - no deadline

user: fhlavac
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_10087: state: open
title: Bug - react-code-editor - resizeObserver resize loop
body: **Describe the problem**
I am rendering a simple react-code-editor component. If my browser's zoom level is less than 100%, I seem to get infinite resizeObserver errors thrown with the message: "ResizeObserver loop completed with undelivered notifications."

"@patternfly/react-code-editor": "5.2.0",
"monaco-editor": "0.45.0",
"react-monaco-editor": "^0.55.0",

**How do you reproduce the problem?**
- Run react application in webpack with dev error overlay enabled.

- Render:
```
import React from 'react';
import { CodeEditor, Language } from '@patternfly/react-code-editor';
import { editor } from 'monaco-editor/esm/vs/editor/editor.api';

export const ValuesCodeEditor = ({ code }: { code: string }) => {
  const onEditorDidMount = (editor: editor.IStandaloneCodeEditor) => {
    editor.layout();
    editor.focus();
  };

  return (
    <CodeEditor
      isLineNumbersVisible={false}
      isReadOnly
      code={code}
      language={Language.json}
      onEditorDidMount={onEditorDidMount}
      height="400px"
    />
  );
};
```

- Reduce your browser's zoom level to 90%.
- Observe the errors thrown.

It looks like this may have been introduced[ with this change.](https://github.com/patternfly/patternfly-react/pull/6547/files#diff-f2348cadb94d70d79f6c3b4844987bde5f08d9776a1da7b6a810e80a244b793eR297)

**Expected behavior**
No resize observer error thrown

**Is this issue blocking you?**
Workaround: Keep zoom level at or above 100%.

**Screenshots**
<img width="1567" alt="Screenshot 2024-02-15 at 7 32 16 AM" src="https://github.com/patternfly/patternfly-react/assets/869106/851a9c76-e242-45a7-b8de-b3adc6c49671">


**What is your environment?**
 - OS: [e.g. iOS]. MacOS
 - Browser [e.g. chrome, safari] Chrome
 - Version [e.g. 22]

**What is your product and what release date are you targeting?**
OCM

**Any other information?**
With some trial and error, it appears that [debouncing the handleResize method](https://github.com/patternfly/patternfly-react/blob/5e4e4806b55077f52997c5a6c4e55e39c14947ea/packages/react-core/src/helpers/resizeObserver.tsx#L86) in the getResizeObserver function fixes the issue.
```
// handleResize();
debounce(handleResize, 100);
```

user: jschuler
issue_10086: state: open
title: fix(Popper): check for undefined
body: **What**: Closes #9936

@nicolethoen I guess this should fix the error, when I try to reproduce the bug in patternfly runtime, I get the `children is undefined` error right away from the docs build, so I cannot reproduce the bug properly

<img width="395" alt="Screenshot 2024-02-14 at 10 31 18" src="https://github.com/patternfly/patternfly-react/assets/84135613/813864ae-edf1-415e-b231-75400e5bb60d">

user: adamviktora
issue_10085: state: open
title: Checkbox - add examples of "Reversed" and "Label wraps"
body: **Describe the enhancement or change**
Add two examples to Checkbox component - Reversed and Label wraps, as it is done in Radio: https://www.patternfly.org/components/forms/radio#reversed, https://www.patternfly.org/components/forms/radio#reversed

Should be done in `main` branch.

(created based on this comment: https://github.com/patternfly/patternfly-react/pull/10016#issuecomment-1934507656)

user: adamviktora
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_10083: state: open
title: Dropdown - expose max height props
body: **Describe the enhancement or change**
A clear and concise description of the request. What is the expected outcome?
Max height can not be set on the dropdown and spread to menu content

user: tlabaj
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_10076: state: open
title: Calendar month - broken link in docs
body: This link is hard coded to `/v4` - should probably be a relative link instead?

https://github.com/patternfly/patternfly-react/blob/8152e851ddfb649ab2ae4b4405d848e74416f771/packages/react-core/src/components/CalendarMonth/examples/CalendarMonth.md?plain=1#L20

Can be updated with https://github.com/patternfly/patternfly-react/issues/9998
user: mcoker
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_10075: state: open
title: bug(Select): expose height and max height props for Menu content
body: <!-- What changes are being made? Please link the issue being addressed. -->
**What**: Closes #9847 

<!-- Are there any upstream issues or separate issues you need to reference? -->
**Additional issues**:

user: tlabaj
issue_10073: state: open
title: feat(Label): add status, update examples
body: <!-- What changes are being made? Please link the issue being addressed. -->
**What**: Closes #10047

- Adds `status` prop. `color` does not override the color provided by `status`, but `icon` will override the default status icon.
- Adds `pf-m-filled` when variant is `filled`
- Updates examples with new status labels & changes non-status label icons to CubeIcon
user: kmcfaul
issue_10071: state: open
title: Update popover in Password Strength demo
body: **Describe the enhancement or change**
Currently the popover in the Password Strength has content related to mentioning password requirements. In general that sort of content shouldn't be hidden in a popover and instead displayed below the input, which the demo is already doing.

We should either remove the help popover or update its content to something more along the lines of "why does a strong password matter" or something along those lines.

**Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?**

**Any other information?**

user: thatblindgeye
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_10070: state: open
title: bug(Nav): Fixed scroll buttons always showing
body: <!-- What changes are being made? Please link the issue being addressed. -->
**What**: Closes #9977 

`pf-m-scrollable`  is no longer hiding the buttons.  Updated React to hide them instead.

user: tlabaj
issue_10069: state: open
title: Patternfly widgets
body: Package name TBD but temporarily `patternfly-widgets`.

- [ ] #10109
- [ ] [Update patternfly-org/react-docs to pull in new package for documentation](https://github.com/patternfly/patternfly-org/issues/3898)
- [ ] #10111
- [ ] Create CheckboxSelect widget & example
- [ ] Create TypeaheadSelect widget & example

user: kmcfaul
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_10067: state: open
title: Bug - Tabs - Nested Tab demo broken
body: https://www.patternfly.org/components/tabs/react-demos#nested-tabs

There is a `ReferenceError: sizing is not defined`.
Even the full page screenshot is wrong.
user: nicolethoen
issue_10066: state: open
title: fix(MenuToggle): fix indeterminate checkbox error, toggle click behavior
body: <!-- What changes are being made? Please link the issue being addressed. -->
**What**: Closes #10034 and #10035

For 10034 - `checked` needed to use the result of `calculateChecked` instead of just the `isChecked` prop (because `null` needs to be re-resolved to `false` to prevent the issue). 

For 10035 - This one is a little tricky, because the new toggle structure was not set up to wrap or pass the toggle click handler to the `splitButtonItems`. I've opted to put the onClick on the outer div wrapper, and prevent propagation in the splitButtonItems (on the action button and checkbox input specifically), but we may want to consider which behavior we want. We can use the changes in the PR currently (the whole div becomes clickable), or make the checkbox label text click trigger the checkbox input change handler instead (keeping the toggle button as the only toggle click handler), or let a user pass the `onClick` manually to the MenuToggleCheckbox.

user: kmcfaul
issue_10065: state: open
title: CodeEditor - allow additional props to pass to Editor
body: There was an issue in slack where the new `@monaco-editor/react` package isn't playing nicely with the `monaco-yaml` package's autocomplete feature. It seems a possible resolution would be to pass a `beforeMount` callback to the `Editor` to allow `monaco-yaml` to configure the editor before the initial mount, but currently we do not expose that prop or spread any additional props to `Editor`.
user: kmcfaul
issue_10061: state: open
title: Bug - DatePicker - not revalidated on change to validators prop
body: **Describe the problem**
If the `validators` prop is changed, the `DatePicker` does not re-run the validation.

**How do you reproduce the problem?**
The [Date and time range picker](https://www.patternfly.org/components/date-and-time/date-and-time-picker#date-and-time-range-picker) example can be used to demonstrate this issue. Enter a “to” date that is before the “from” date, and observe the validation error appear. Then change the “from” date to be before the “to” date. The validation error does not go away until you tab into and then out of the “to” date field.

**Expected behavior**
If the field has already been validated at least one due to text entry or losing focus, then the validation should occur again if the validation functions change.

**Is this issue blocking you?**
For now we need to perform validation outside of the component and add our own helper text.


**What is your environment?**
 - Version 5

**What is your product and what release date are you targeting?**
OpenShift Cluster Manager UI - continuous release

user: KevinFCormier
issue_10060: state: open
title: Add toggle example description and/or revisit the isToggle prop for Badge
body: **Describe the enhancement or change**
Followup to comment chain https://github.com/patternfly/patternfly-react/pull/10051#discussion_r1471978692

We should add a description to the new example added in the above linked PR, if we intend to keep the API as it stands in that PR, just to warn that consumers must pass a toggle variant badge to our MenuToggle component. Without doing so, the badge would be inaccessible even if onClick handler is added to it since it's only a span.

**Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?**

**Any other information?**
Update: we should take a look at whether we want to keep the isToggle prop on the Badge after alpha, but before release
user: thatblindgeye
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_10059: state: open
title: ToggleGroup - add iconPosition prop
body: **Is this a new component or an extension of an existing one?**
Toggle group

**Describe the feature**
Followup to https://github.com/patternfly/patternfly-react/pull/10019
Similar to our Button component, we should add a prop to position the icon in a toggle group item so that it can come before or after the toggle item text (if any). The prop should only accept values "start" and "end" (Button/any other components should have deprecated "left" and "right" values)

**Are there visuals for this feature? If applicable, please include examples for each state and for varying widths**
Include screenshots or links to Marvel or other mockups.

**Any other information?**

user: thatblindgeye
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_10058: state: open
title: Bug - HelperText - props table not rendering in 
body: **Describe the problem**
Mentioned in comment https://github.com/patternfly/patternfly-react/pull/10029#pullrequestreview-1856625656 , the props table for HelperText isn't rendering in the v6 branch.

**How do you reproduce the problem?**
Go to the [Helper Text props in v6 staging](https://patternfly-react-v6.surge.sh/components/helper-text#props)

**Expected behavior**
A clear and concise description of the expected behavior.

**Is this issue blocking you?**
List the workaround if there is one.

**Screenshots**
If applicable, add screenshots to help explain the issue.

**What is your environment?**
 - OS: [e.g. iOS]
 - Browser [e.g. chrome, safari]
 - Version [e.g. 22]

**What is your product and what release date are you targeting?**

**Any other information?**

user: thatblindgeye
issue_10057: state: open
title: Table - empty/non-text Th components need a11y updates
body: **Describe the problem**
Related to https://github.com/patternfly/patternfly/issues/6272
A concern with our selectable with checkbox Table implementation was brought to us, with the "select all rows" checkbox in the `thead` being flagged by Lighthouse/Browserstack, as well as the fact that React's `Th` component was being transformed into a `td` element unexpectedly. This - in addition to empty `td` elements being used in the `thead`, as seen in our "Actions" example - was cause for concern regarding whether the output from screen readers may be confusing/inaccessible.

**How do you reproduce the problem?**
Test either our [selectable with checkbox](https://www.patternfly.org/components/table#selectable-with-checkbox) example or [actions table example](https://www.patternfly.org/components/table#actions) with Lighthouse/browserstack and/or screen reader. An issue may be flagged for `td` elements needing a table header in tables larger than 3x3, or the output from screen reader may be confusing/not provide enough context.

**Any other information?**
In order to resolve issues mentioned here:

- [ ] The Th/selectable utility logic needs to be updated to prevent a Th component from being transformed into a `td` element
- [ ] All examples need to be updated to use a Th inside of the Thead component; no longer should we use a Td
  - [ ] If a Th component is intended to be visually empty (such as in our "Actions" example), visually-hidden/screen reader text MUST be passed to the Th. This will preserve the visual design, while also avoiding the error of an empty Th + providing improved context via assistive tech.
    ```
    <Th>
      <span class="pf-v5-screen-reader">Visually hidden header text</span>
    </Th>
    ````
  - [ ] If a Th component contains non-text, interactive content (checkbox, expand all toggle, etc), in addition to the interactive element requiring an aria-label, the Th should have an aria-label as well. In a case like our "select all rows" checkbox, without the Th's aria-label then other checkbox cells end up being announced as, "Select row 0, select all rows". By adding an aria-label such as "Row select", the announcement becomes "Row select, select row 0" (or in the case of the select all checkbox, "Row select, select all rows").
    ```
    <Th aria-label="Row select">
      <label><input  type="checkbox" aria-label="Select all rows" /></label>
    </Th>
    ````
user: thatblindgeye
issue_10055: state: open
title: Use plain, no-padding button on form help icon
body: There are various demos and examples that use a button for the help icon on the form label - these should be changed to a plain, no padding button.

Known spots:
- [ ] Form examples
- [ ] Password strength examples
user: srambach
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_10054: state: open
title: Card:  Combine isCompact and isLarge into one prop
body: **Describe the enhancement or change**
Combine isCompact and isLarge into one prop since only one can be applied at a time.  Then we can remove console warning.

user: tlabaj
labels: breaking change :boom:: this change requires a major release and has API changes.
Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_10052: state: open
title: Add secondary variant to Sidebar example
body: **Describe the enhancement or change**
To match Core we should either add a new example or update an existing example to use the "secondary" backgroundVariant for Sidebar and SidebarPanel

**Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?**

**Any other information?**

user: thatblindgeye
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_10050: state: open
title: Chore(Skeleton): Adding demo to match core
body: **What**: Closes #7214 

user: gabipodolnikova
issue_10053: state: open
title: Bug - Truncate - tooltip also shows when there is no actual truncation
body: The [Truncate](https://www.patternfly.org/components/truncate) component always has a active tooltip for its content, even when there is no actual need for truncation:

![image](https://github.com/patternfly/patternfly/assets/3228183/c4a932a3-95d8-4047-a60b-94ecd2364c86)

Such a tooltip doesn't contribute anything to the user experience, but is an annoyance especially if there are many of them.

It would be great if `Truncate` would only have a tooltip when truncation does actually take place.

Alternatively, as a lesser alternative, a property would be welcome that allows the programmer to disable the tooltip completely.
user: mvollmer
issue_10047: state: open
title: Label - status labels
body: Add new status labels coming in from core to react for penta.

user: kmcfaul
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_10046: state: open
title: Generate dist/dynamic-modules.json for relevant packages
body: This PR modifies `scripts/build-single-packages.js` so that it also generates a `dist/dynamic-modules.json` file for each package containing dynamic modules.

```sh
$ find . -name dynamic-modules.json
./packages/react-charts/dist/dynamic-modules.json
./packages/react-core/dist/dynamic-modules.json
./packages/react-icons/dist/dynamic-modules.json
./packages/react-table/dist/dynamic-modules.json 
```

We generate `dynamic-modules.json` files to make it easier for consuming projects to share specific PatternFly dynamic modules (instead of sharing the whole package indexes) via [webpack module federation](https://webpack.js.org/concepts/module-federation/).

Each `dynamic-modules.json` file maps package index exports to their corresponding dynamic modules, for example:

```jsonc
// packages/react-core/dist/dynamic-modules.json
{
  "ASTERISK": "dist/dynamic/helpers/htmlConstants",
  "AboutModal": "dist/dynamic/components/AboutModal",
  "AboutModalProps": "dist/dynamic/components/AboutModal",
  "Accordion": "dist/dynamic/components/Accordion",
  "AccordionContent": "dist/dynamic/components/Accordion",
  "AccordionContentProps": "dist/dynamic/components/Accordion",
  "AccordionExpandableContentBody": "dist/dynamic/components/Accordion",
  "AccordionExpandableContentBodyProps": "dist/dynamic/components/Accordion",
  "AccordionItem": "dist/dynamic/components/Accordion",
  "AccordionItemProps": "dist/dynamic/components/Accordion",
  "AccordionProps": "dist/dynamic/components/Accordion",
  "AccordionToggle": "dist/dynamic/components/Accordion",
  "AccordionToggleProps": "dist/dynamic/components/Accordion",
  // ...
}
```

The algorithm that parses dynamic module information favors non-deprecated modules with most specific file paths, for example `dist/dynamic/components/Wizard/hooks` is favored over `dist/dynamic/components/Wizard`.

Note: this code is ported from openshift/console#13521
user: vojtechszocs
issue_10038: state: open
title: Bug - DragDrop - basic example isn't reordering
body: The current/non-dndkit drag and drop isn't reordering in the basic example on a drop event. The multiple lists example does reorder when an item is dragged and dropped within the same list however, so it seems to be a state update that's not happening in the basic example.
user: kmcfaul
issue_10035: state: open
title: Bug - MenuToggleCheckbox - events not generated when clicking on text
body: Trying to replace the deprecated `Dropdown`, for an existing bulk select, and running into trouble.

After a selection, the user cannot click on the "10 selected" text below to expand the list. We can only click on the down arrow to expand the list.

![chrome-capture-2024-0-23](https://github.com/patternfly/patternfly-react/assets/17481322/a25fa4d4-700d-4803-9347-4b44006f6052)


As a workaround, I wrapped the "10 selected" text in a `span` and used its `onClick` to open the list. However, this does not seem correct. I expected the `onClick` of `MenuToggle` to be triggered.

**Notes**

When the text is clicked:
- the `onSelect` of `Dropdown` isn't called 
- the `onClick` of `MenuToggle` isn't called
- neither `onChange` or `onClick` of `MenuToggleCheckbox` are called

With the older, deprecated `Dropdown` / `DropdownToggleCheckbox`, I'm able to click anywhere on the text / dropdown. 

**Code**
![Screenshot 2024-01-23 at 11 13 22 AM](https://github.com/patternfly/patternfly-react/assets/17481322/2af4f82d-1297-4836-9759-8d96d8391418)


user: dlabrecq
issue_10034: state: open
title: Bug - MenuToggleCheckbox - indeterminate console error
body: Setting the checkbox to be indeterminate via `isChecked={null}` is triggering an error that indicates a "controlled input is becoming uncontrolled" in the console.

To resolve - `checked` should be set by `calculateChecked` instead.

Also, the error was not showing on the docs site but is showing on codesandbox.
user: kmcfaul
issue_10025: state: open
title: Bug - Select - validated
body: The v4 `Select` supported a `validated` property; however, it has been omitted for v5. The [design guidelines](https://www.patternfly.org/components/menus/select/design-guidelines#select-lists-with-validation) currently state the "Select component offers three validation-state presentations", but I don't see how the ["validated selections" example](https://www.patternfly.org/components/menus/select/react-deprecated#validated-selections) is achieved in v5?

We've been using validation in Cost Management, but are blocked from updating to the v5 `Select`.

**Cost Management snapshot**
<img width="391" alt="Screenshot 2024-01-19 at 9 19 55 AM" src="https://github.com/patternfly/patternfly-react/assets/17481322/d8291539-549f-4c2c-8adc-1f033a589fd0">

user: dlabrecq
issue_10016: state: open
title: Consume core Penta updates: Form controls, checkbox, radio
body: **What**: Closes #9931, closes #10055

Things done:
- introduced `FormGroupLabelHelp` component to make using `labelIcon` prop simple
- added some spaces next to label in **FormGroup** to look similar to core

Breaking changes done:
- renamed `labelIcon` prop in **FormGroup** to `labelHelp`
- renamed `isLabelBeforeButton` prop in **Checkbox/Radio** to `labelPosition?: 'start' | 'end'`

Todo:
- update examples of **Checkbox** to show `isLabelWrapped` and `labelPosition="start"` (issue: https://github.com/patternfly/patternfly-react/issues/10085)
- (add Form control examples in React too)
user: adamviktora
labels: breaking change :boom:: this change requires a major release and has API changes.
issue_10014: state: open
title: Expand all, not just section for Navigation - Expand all icon for the navigation for observability of items
body: This is an extension to existing [navigation component](https://www.patternfly.org/components/navigation)

In Red Hat Insights that lives on console.redhat.com we would like to provide an expand all button for the whole navigation. So pretty much the expected behaviour is to have a single click expand button in the navigation so all the items within the navigation expand.
The benefit of this is observability and quick findability of the desired page. Saves two or three clicks, based on how deep the navigation item is hidden. And for new customers they can get a quick peek into what is in the navigation itself.

I believe currently these is only expandable section, and no expand all for everything for navigation.

![image](https://github.com/patternfly/patternfly-react/assets/78739379/03b8ccd7-3c66-4e78-81f2-3a386359ee46)


user: kuklas
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_10012: state: open
title: Consume tokens: Overflow menu
body: Depends on https://github.com/patternfly/patternfly-react/issues/9985 and https://github.com/patternfly/patternfly-react/issues/9986 https://github.com/patternfly/patternfly/issues/6166
user: tlabaj
issue_10011: state: open
title: Consume tokens: Select
body: Depends on  https://github.com/patternfly/patternfly-react/issues/9985 and https://github.com/patternfly/patternfly-react/issues/9986 
user: tlabaj
issue_10010: state: open
title: Consume core updates: Tree view  ( Follow up to issue)
body: Follow up to issue issue https://github.com/patternfly/patternfly/issues/5723

Updated in PR #10081 to fix build : 
-  `selectable` modifier removed, using a string now.
user: tlabaj
issue_10009: state: open
title: Consume core updates: Wizard ( Follow up to issue)
body: follow up to core issue https://github.com/patternfly/patternfly/issues/5742
user: tlabaj
issue_10008: state: open
title: Consume core updates: Dual list selector ( Follow up to issue)
body: Follow up to core issue https://github.com/patternfly/patternfly/issues/5741
user: tlabaj
issue_9986: state: open
title: Consume Penta tokens: Menu toggle
body: Follow up to core PR https://github.com/patternfly/patternfly/pull/6177
user: tlabaj
issue_9985: state: open
title: Consume Penta tokens: Menu
body: Follow up to core  PR https://github.com/patternfly/patternfly/pull/6167

Updated in PR #10081 to fix build
- `Menu` `favorite`, `nav`, `text`, `focus` modifiers removed, using a string now. `focus` should probably be added back.
user: tlabaj
issue_9984: state: open
title: Consume core updates: Menu, Menu Toggle, Dropdown, Select, Overflow Menu (exclude deprecated Context Selector, Application Launcher, Options menu( Follow up to issue)
body: Follow up to core issue https://github.com/patternfly/patternfly/issues/5718

```[tasklist]
### Tasks
- [ ] https://github.com/patternfly/patternfly-react/issues/9985
- [ ] https://github.com/patternfly/patternfly-react/issues/9986
- [ ] https://github.com/patternfly/patternfly-react/issues/10011
- [ ] https://github.com/patternfly/patternfly-react/issues/10012
```

user: tlabaj
issue_9977: state: open
title: Bug - [v6 Nav] - horizontal subnav scroll button 
body: **Describe the problem**
A clear and concise description of the problem. Which components are affected?
Follow up to comment in PR  https://github.com/patternfly/patternfly-react/pull/9948#pullrequestreview-1818940554

Nav scroll buttons always showing.  They should be hidden when there is no scrollable content. 
user: tlabaj
issue_9974: state: open
title: feat(SearchInput): Add ability to add id to input in SearchInput component
body: <!-- What changes are being made? Please link the issue being addressed. -->
**What**: Closes #9824 


user: jessiehuff
issue_9970: state: open
title: chore(deps): update devdependencies
body: [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [@babel/core](https://babel.dev/docs/en/next/babel-core) ([source](https://togithub.com/babel/babel/tree/HEAD/packages/babel-core)) | [`7.23.7` -> `7.23.9`](https://renovatebot.com/diffs/npm/@babel%2fcore/7.23.7/7.23.9) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@babel%2fcore/7.23.9?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@babel%2fcore/7.23.9?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@babel%2fcore/7.23.7/7.23.9?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@babel%2fcore/7.23.7/7.23.9?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@babel/eslint-parser](https://babel.dev/) ([source](https://togithub.com/babel/babel/tree/HEAD/eslint/babel-eslint-parser)) | [`7.23.3` -> `7.23.10`](https://renovatebot.com/diffs/npm/@babel%2feslint-parser/7.23.3/7.23.10) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@babel%2feslint-parser/7.23.10?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@babel%2feslint-parser/7.23.10?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@babel%2feslint-parser/7.23.3/7.23.10?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@babel%2feslint-parser/7.23.3/7.23.10?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@babel/plugin-proposal-decorators](https://babel.dev/docs/en/next/babel-plugin-proposal-decorators) ([source](https://togithub.com/babel/babel/tree/HEAD/packages/babel-plugin-proposal-decorators)) | [`7.23.7` -> `7.23.9`](https://renovatebot.com/diffs/npm/@babel%2fplugin-proposal-decorators/7.23.7/7.23.9) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@babel%2fplugin-proposal-decorators/7.23.9?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@babel%2fplugin-proposal-decorators/7.23.9?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@babel%2fplugin-proposal-decorators/7.23.7/7.23.9?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@babel%2fplugin-proposal-decorators/7.23.7/7.23.9?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@babel/preset-env](https://babel.dev/docs/en/next/babel-preset-env) ([source](https://togithub.com/babel/babel/tree/HEAD/packages/babel-preset-env)) | [`7.23.8` -> `7.23.9`](https://renovatebot.com/diffs/npm/@babel%2fpreset-env/7.23.8/7.23.9) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@babel%2fpreset-env/7.23.9?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@babel%2fpreset-env/7.23.9?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@babel%2fpreset-env/7.23.8/7.23.9?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@babel%2fpreset-env/7.23.8/7.23.9?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| @&#8203;patternfly/documentation-framework | [`5.3.18` -> `5.4.3`](https://renovatebot.com/diffs/npm/@patternfly%2fdocumentation-framework/5.3.18/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@patternfly%2fdocumentation-framework/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@patternfly%2fdocumentation-framework/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@patternfly%2fdocumentation-framework/5.3.18/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@patternfly%2fdocumentation-framework/5.3.18/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@types/jest](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/jest) ([source](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/jest)) | [`29.5.11` -> `29.5.12`](https://renovatebot.com/diffs/npm/@types%2fjest/29.5.11/29.5.12) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@types%2fjest/29.5.12?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@types%2fjest/29.5.12?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@types%2fjest/29.5.11/29.5.12?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@types%2fjest/29.5.11/29.5.12?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@types/react](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react) ([source](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react)) | [`18.2.48` -> `18.2.60`](https://renovatebot.com/diffs/npm/@types%2freact/18.2.48/18.2.60) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@types%2freact/18.2.60?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@types%2freact/18.2.60?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@types%2freact/18.2.48/18.2.60?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@types%2freact/18.2.48/18.2.60?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@types/react-dom](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-dom) ([source](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-dom)) | [`18.2.18` -> `18.2.19`](https://renovatebot.com/diffs/npm/@types%2freact-dom/18.2.18/18.2.19) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@types%2freact-dom/18.2.19?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@types%2freact-dom/18.2.19?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@types%2freact-dom/18.2.18/18.2.19?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@types%2freact-dom/18.2.18/18.2.19?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [eslint](https://eslint.org) ([source](https://togithub.com/eslint/eslint)) | [`8.56.0` -> `8.57.0`](https://renovatebot.com/diffs/npm/eslint/8.56.0/8.57.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/eslint/8.57.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/eslint/8.57.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/eslint/8.56.0/8.57.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/eslint/8.56.0/8.57.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [eslint-plugin-jest](https://togithub.com/jest-community/eslint-plugin-jest) | [`27.6.3` -> `27.9.0`](https://renovatebot.com/diffs/npm/eslint-plugin-jest/27.6.3/27.9.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/eslint-plugin-jest/27.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/eslint-plugin-jest/27.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/eslint-plugin-jest/27.6.3/27.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/eslint-plugin-jest/27.6.3/27.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [prettier](https://prettier.io) ([source](https://togithub.com/prettier/prettier)) | [`3.2.2` -> `3.2.5`](https://renovatebot.com/diffs/npm/prettier/3.2.2/3.2.5) | [![age](https://developer.mend.io/api/mc/badges/age/npm/prettier/3.2.5?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/prettier/3.2.5?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/prettier/3.2.2/3.2.5?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/prettier/3.2.2/3.2.5?slim=true)](https://docs.renovatebot.com/merge-confidence/) |

---

### Release Notes

<details>
<summary>babel/babel (@&#8203;babel/core)</summary>

### [`v7.23.9`](https://togithub.com/babel/babel/blob/HEAD/CHANGELOG.md#v7239-2024-01-25)

[Compare Source](https://togithub.com/babel/babel/compare/v7.23.7...v7.23.9)

##### :bug: Bug Fix

-   `babel-helper-transform-fixture-test-runner`, `babel-plugin-transform-function-name`, `babel-plugin-transform-modules-systemjs`, `babel-preset-env`
    -   [#&#8203;16225](https://togithub.com/babel/babel/pull/16225) fix: `systemjs` re-traverses helpers ([@&#8203;liuxingbaoyu](https://togithub.com/liuxingbaoyu))
-   `babel-helper-create-class-features-plugin`, `babel-plugin-proposal-decorators`
    -   [#&#8203;16226](https://togithub.com/babel/babel/pull/16226) Improve decorated private method check ([@&#8203;JLHwung](https://togithub.com/JLHwung))
-   `babel-plugin-proposal-decorators`, `babel-plugin-transform-async-generator-functions`, `babel-plugin-transform-runtime`, `babel-preset-env`
    -   [#&#8203;16224](https://togithub.com/babel/babel/pull/16224) Properly sort `core-js@3` imports ([@&#8203;nicolo-ribaudo](https://togithub.com/nicolo-ribaudo))
-   `babel-traverse`
    -   [#&#8203;15383](https://togithub.com/babel/babel/pull/15383) fix: Don't throw in `getTypeAnnotation` when using TS+inference ([@&#8203;liuxingbaoyu](https://togithub.com/liuxingbaoyu))
-   Other
    -   [#&#8203;16210](https://togithub.com/babel/babel/pull/16210) \[eslint] Fix `no-use-before-define` for class ref in fields ([@&#8203;nicolo-ribaudo](https://togithub.com/nicolo-ribaudo))

##### :house: Internal

-   `babel-core`, `babel-parser`, `babel-template`
    -   [#&#8203;16222](https://togithub.com/babel/babel/pull/16222) Migrate `eslint-parser` to cts ([@&#8203;liuxingbaoyu](https://togithub.com/liuxingbaoyu))
-   `babel-types`
    -   [#&#8203;16213](https://togithub.com/babel/babel/pull/16213) Remove `@babel/types` props that are not produced by the parser ([@&#8203;liuxingbaoyu](https://togithub.com/liuxingbaoyu))

##### :running_woman: Performance

-   `babel-parser`
    -   [#&#8203;16072](https://togithub.com/babel/babel/pull/16072) perf: Improve parser performance for typescript ([@&#8203;liuxingbaoyu](https://togithub.com/liuxingbaoyu))

##### :microscope: Output optimization

-   `babel-helper-create-class-features-plugin`, `babel-plugin-proposal-decorators`, `babel-plugin-proposal-destructuring-private`, `babel-plugin-proposal-pipeline-operator`, `babel-plugin-transform-class-properties`, `babel-plugin-transform-class-static-block`, `babel-plugin-transform-new-target`, `babel-plugin-transform-parameters`, `babel-plugin-transform-private-methods`, `babel-preset-env`
    -   [#&#8203;16218](https://togithub.com/babel/babel/pull/16218) Improve temporary variables for decorators ([@&#8203;liuxingbaoyu](https://togithub.com/liuxingbaoyu))
-   `babel-helpers`, `babel-plugin-proposal-explicit-resource-management`, `babel-runtime-corejs2`, `babel-runtime-corejs3`, `babel-runtime`
    -   [#&#8203;15959](https://togithub.com/babel/babel/pull/15959) Improve output of `using` ([@&#8203;liuxingbaoyu](https://togithub.com/liuxingbaoyu))

</details>

<details>
<summary>eslint/eslint (eslint)</summary>

### [`v8.57.0`](https://togithub.com/eslint/eslint/releases/tag/v8.57.0)

[Compare Source](https://togithub.com/eslint/eslint/compare/v8.56.0...v8.57.0)

#### Features

-   [`1120b9b`](https://togithub.com/eslint/eslint/commit/1120b9b7b97f10f059d8b7ede19de2572f892366) feat: Add loadESLint() API method for v8 ([#&#8203;18098](https://togithub.com/eslint/eslint/issues/18098)) (Nicholas C. Zakas)
-   [`dca7d0f`](https://togithub.com/eslint/eslint/commit/dca7d0f1c262bc72310147bcefe1d04ecf60acbc) feat: Enable `eslint.config.mjs` and `eslint.config.cjs` ([#&#8203;18066](https://togithub.com/eslint/eslint/issues/18066)) (Nitin Kumar)

#### Bug Fixes

-   [`2196d97`](https://togithub.com/eslint/eslint/commit/2196d97094ba94d6d750828879a29538d1600de5) fix: handle absolute file paths in `FlatRuleTester` ([#&#8203;18064](https://togithub.com/eslint/eslint/issues/18064)) (Nitin Kumar)
-   [`69dd1d1`](https://togithub.com/eslint/eslint/commit/69dd1d1387b7b53617548d1f9f2c149f179e6e17) fix: Ensure config keys are printed for config errors ([#&#8203;18067](https://togithub.com/eslint/eslint/issues/18067)) (Nitin Kumar)
-   [`9852a31`](https://togithub.com/eslint/eslint/commit/9852a31edcf054bd5d15753ef18e2ad3216b1b71) fix: deep merge behavior in flat config ([#&#8203;18065](https://togithub.com/eslint/eslint/issues/18065)) (Nitin Kumar)
-   [`4c7e9b0`](https://togithub.com/eslint/eslint/commit/4c7e9b0b539ba879ac1799e81f3b6add2eed4b2f) fix: allow circular references in config ([#&#8203;18056](https://togithub.com/eslint/eslint/issues/18056)) (Milos Djermanovic)

#### Documentation

-   [`84922d0`](https://togithub.com/eslint/eslint/commit/84922d0bfa10689a34a447ab8e55975ff1c1c708) docs: Show prerelease version in dropdown ([#&#8203;18139](https://togithub.com/eslint/eslint/issues/18139)) (Nicholas C. Zakas)
-   [`5b8c363`](https://togithub.com/eslint/eslint/commit/5b8c3636a3d7536535a6878eca0e5b773e4829d4) docs: Switch to Ethical Ads ([#&#8203;18117](https://togithub.com/eslint/eslint/issues/18117)) (Milos Djermanovic)
-   [`77dbfd9`](https://togithub.com/eslint/eslint/commit/77dbfd9887b201a46fc68631cbde50c08e1a8dbf) docs: show NEXT in version selectors ([#&#8203;18052](https://togithub.com/eslint/eslint/issues/18052)) (Milos Djermanovic)

#### Chores

-   [`1813aec`](https://togithub.com/eslint/eslint/commit/1813aecc4660582b0678cf32ba466eb9674266c4) chore: upgrade [@&#8203;eslint/js](https://togithub.com/eslint/js)[@&#8203;8](https://togithub.com/8).57.0 ([#&#8203;18143](https://togithub.com/eslint/eslint/issues/18143)) (Milos Djermanovic)
-   [`5c356bb`](https://togithub.com/eslint/eslint/commit/5c356bb0c6f53c570224f8e9f02c4baca8fc6d2f) chore: package.json update for [@&#8203;eslint/js](https://togithub.com/eslint/js) release (Jenkins)
-   [`f4a1fe2`](https://togithub.com/eslint/eslint/commit/f4a1fe2e45aa1089fe775290bf530de82f34bf16) test: add more tests for ignoring files and directories ([#&#8203;18068](https://togithub.com/eslint/eslint/issues/18068)) (Nitin Kumar)
-   [`42c0aef`](https://togithub.com/eslint/eslint/commit/42c0aefaf6ea8b998b1c6db61906a79c046d301a) ci: Enable CI for `v8.x` branch ([#&#8203;18047](https://togithub.com/eslint/eslint/issues/18047)) (Milos Djermanovic)

</details>

<details>
<summary>jest-community/eslint-plugin-jest (eslint-plugin-jest)</summary>

### [`v27.9.0`](https://togithub.com/jest-community/eslint-plugin-jest/blob/HEAD/CHANGELOG.md#2790-2024-02-16)

[Compare Source](https://togithub.com/jest-community/eslint-plugin-jest/compare/v27.8.0...v27.9.0)

##### Features

-   add should-be-fine support for flat configs ([#&#8203;1505](https://togithub.com/jest-community/eslint-plugin-jest/issues/1505)) ([4cc2a1b](https://togithub.com/jest-community/eslint-plugin-jest/commit/4cc2a1b680507ff006b5d2b02fa6d262584bb263))

### [`v27.8.0`](https://togithub.com/jest-community/eslint-plugin-jest/blob/HEAD/CHANGELOG.md#2780-2024-02-13)

[Compare Source](https://togithub.com/jest-community/eslint-plugin-jest/compare/v27.7.0...v27.8.0)

##### Features

-   support `failing.each` ([#&#8203;1499](https://togithub.com/jest-community/eslint-plugin-jest/issues/1499)) ([9e9cf83](https://togithub.com/jest-community/eslint-plugin-jest/commit/9e9cf8302ae182402da853a11b05e1560ccc63ee))

### [`v27.7.0`](https://togithub.com/jest-community/eslint-plugin-jest/blob/HEAD/CHANGELOG.md#2770-2024-02-13)

[Compare Source](https://togithub.com/jest-community/eslint-plugin-jest/compare/v27.6.3...v27.7.0)

##### Features

-   allow `[@typescript-eslint](https://togithub.com/typescript-eslint)` v7 ([#&#8203;1500](https://togithub.com/jest-community/eslint-plugin-jest/issues/1500)) ([6be2928](https://togithub.com/jest-community/eslint-plugin-jest/commit/6be2928816c69afca88a598e302910b113068ee9))

#### [27.6.3](https://togithub.com/jest-community/eslint-plugin-jest/compare/v27.6.2...v27.6.3) (2024-01-12)

##### Bug Fixes

-   replace use of deprecated methods ([#&#8203;1453](https://togithub.com/jest-community/eslint-plugin-jest/issues/1453)) ([9204a51](https://togithub.com/jest-community/eslint-plugin-jest/commit/9204a51b4a43541e5e59c6c7fb3a3da1e2d49c2b))

#### [27.6.2](https://togithub.com/jest-community/eslint-plugin-jest/compare/v27.6.1...v27.6.2) (2024-01-10)

##### Reverts

-   Revert "chore: use relative path to parent `tsconfig.json` ([#&#8203;1476](https://togithub.com/jest-community/eslint-plugin-jest/issues/1476))" ([5e6199d](https://togithub.com/jest-community/eslint-plugin-jest/commit/5e6199d62154e21ccc732bc09d8bbb87bd3ef748)), closes [#&#8203;1476](https://togithub.com/jest-community/eslint-plugin-jest/issues/1476)

#### [27.6.1](https://togithub.com/jest-community/eslint-plugin-jest/compare/v27.6.0...v27.6.1) (2024-01-01)

##### Bug Fixes

-   include plugin `meta` information with snapshot processor for ESLint v9 ([#&#8203;1484](https://togithub.com/jest-community/eslint-plugin-jest/issues/1484)) ([067e246](https://togithub.com/jest-community/eslint-plugin-jest/commit/067e246864813fa88933f06628b6ca0ff31ca863))

</details>

<details>
<summary>prettier/prettier (prettier)</summary>

### [`v3.2.5`](https://togithub.com/prettier/prettier/blob/HEAD/CHANGELOG.md#325)

[Compare Source](https://togithub.com/prettier/prettier/compare/3.2.4...3.2.5)

[diff](https://togithub.com/prettier/prettier/compare/3.2.4...3.2.5)

##### Support Angular inline styles as single template literal ([#&#8203;15968](https://togithub.com/prettier/prettier/pull/15968) by [@&#8203;sosukesuzuki](https://togithub.com/sosukesuzuki))

[Angular v17](https://blog.angular.io/introducing-angular-v17-4d7033312e4b) supports single string inline styles.

<!-- prettier-ignore -->

```ts
// Input
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.4
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.5
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `
    h1 {
      color: blue;
    }
  `,
})
export class AppComponent {}

```

##### Unexpected embedded formatting for Angular template ([#&#8203;15969](https://togithub.com/prettier/prettier/pull/15969) by [@&#8203;JounQin](https://togithub.com/JounQin))

Computed template should not be considered as Angular component template

<!-- prettier-ignore -->

```ts
// Input
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.4
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{ hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.5
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}
```

##### Use `"json"` parser for `tsconfig.json` by default ([#&#8203;16012](https://togithub.com/prettier/prettier/pull/16012) by [@&#8203;sosukesuzuki](https://togithub.com/sosukesuzuki))

In [v2.3.0](https://prettier.io/blog/2024/01/12/3.2.0#new-jsonc-parser-added-15831httpsgithubcomprettierprettierpull15831-by-fiskerhttpsgithubcomfisker), we introduced `"jsonc"` parser which adds trialing comma **by default**.

When adding a new parser we also define how it will be used based on the [`linguist-languages`](https://www.npmjs.com/package/linguist-languages) data.

`tsconfig.json` is a special file used by [TypeScript](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html#using-tsconfigjson-or-jsconfigjson), it uses `.json` file extension, but it actually uses the [JSON with Comments](https://code.visualstudio.com/docs/languages/json#\_json-with-comments) syntax. However, we found that there are many third-party tools not recognize it correctly because of the confusing `.json` file extension.

We decide to treat it as a JSON file for now to avoid the extra configuration step.

To keep using the `"jsonc"` parser for your `tsconfig.json` files, add the following to your `.pretterrc` file

```json
{
  "overrides": [
    {
      "files": ["tsconfig.json", "jsconfig.json"],
      "options": {
        "parser": "jsonc"
      }
    }
  ]
}
```

<!-- prettier-ignore -->

```
```

### [`v3.2.4`](https://togithub.com/prettier/prettier/blob/HEAD/CHANGELOG.md#324)

[Compare Source](https://togithub.com/prettier/prettier/compare/3.2.3...3.2.4)

[diff](https://togithub.com/prettier/prettier/compare/3.2.3...3.2.4)

##### Fix incorrect parser inference ([#&#8203;15947](https://togithub.com/prettier/prettier/pull/15947) by [@&#8203;fisker](https://togithub.com/fisker))

Files like `.eslintrc.json` were incorrectly formatted as JSONC files.

<!-- prettier-ignore -->

```jsx
// Input
prettier --file-info .eslintrc.json
{ "ignored": false, "inferredParser": "jsonc" }

// Prettier 3.2.4
prettier --file-info .eslintrc.json
{ "ignored": false, "inferredParser": "json" }
```

### [`v3.2.3`](https://togithub.com/prettier/prettier/blob/HEAD/CHANGELOG.md#323)

[Compare Source](https://togithub.com/prettier/prettier/compare/3.2.2...3.2.3)

[diff](https://togithub.com/prettier/prettier/compare/3.2.2...3.2.3)

##### Throw errors for invalid code ([#&#8203;15881](https://togithub.com/prettier/prettier/pull/15881) by [@&#8203;fisker](https://togithub.com/fisker), [@&#8203;Josh-Cena](https://togithub.com/Josh-Cena), [@&#8203;auvred](https://togithub.com/auvred))

<!-- prettier-ignore -->

```ts
// Input
1++;

// Prettier 3.2.2
1++;

// Prettier 3.2.3
SyntaxError: Invalid left-hand side expression in unary operation (1:1)
> 1 | 1++;
    | ^
```

<!-- prettier-ignore -->

```ts
// Input
try {} catch (error = 1){}

// Prettier 3.2.2
try {
} catch (error) {}

// Prettier 3.2.3
SyntaxError: Catch clause variable cannot have an initializer. (1:23)
> 1 | try {} catch (error = 1){}
    |                       ^
```

##### Fix parser inference ([#&#8203;15927](https://togithub.com/prettier/prettier/pull/15927) by [@&#8203;fisker](https://togithub.com/fisker))

<!-- prettier-ignore -->

```console
// Prettier 3.2.2
prettier --file-info tsconfig.json
{ "ignored": false, "inferredParser": "json" }

// Prettier 3.2.3
prettier --file-info tsconfig.json
{ "ignored": false, "inferredParser": "jsonc" }
```

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/patternfly/patternfly-react).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4xMjcuMCIsInVwZGF0ZWRJblZlciI6IjM3LjIxMi4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->

user: renovate[bot]
issue_9969: state: open
title: Bug - Table - High Visibility Accessibility Issue
body: **Describe the problem**
An unexpected table header element transformation when implementing the 'select all' functionality for checkboxes. Upon attaching a 'select' event handler to the` <Th>` element within the checkbox column's header, the` <Th>` element is converted to a  `<Td>` element in the DOM.
Compromising the table structure creates an accessibility issue as there is no table header(`<Th>`) for a column.

**How do you reproduce the problem?**
Please try to inspect the structure of this table in the DOM.
https://www.patternfly.org/components/table/#selectable-with-checkbox

**Expected behaviour**
The table structure should not be altered on rendering in the DOM.

**Is this issue blocking you?**
https://issues.redhat.com/browse/PCM-12748

**Screenshots**
![Screenshot 2024-01-12 at 3 16 28 PM](https://github.com/patternfly/patternfly-react/assets/49025521/5036225b-f9de-4227-8037-d5f8c0d31db5)


**What is your environment?**
 - OS: Mac OS Sonoma
 - Browser: Chrome
 - Version:  120.0.6099.216

**What is your product and what release date are you targeting?**
Customer Portal

**Any other information?**
As part of the Customer Portal accessibility initiative, we are fixing all the accessibility issues throughout the Customer Portal. So this issue is a high-priority one as it is affecting the accessibility score on all pages which use this table.
user: Arathy-s
issue_9968: state: open
title: A11y Docs Audit: Resolve Critical Axe Violations
body: **Describe the problem**

The Patternfly React docs workspace could use a sweeping accessibility audit to find and resolve axe violations across all PF components.

There are several PF components for which AXE is throwing critical a11y errors.

In RHOAI, critical AXE violations have been noted specifically in [Menu/Application Launcher](https://github.com/patternfly/patternfly-react/issues/8939), and [Tabs](https://patternfly.slack.com/archives/C916H09K4/p1705083591799799)


**How do you reproduce the problem?**

Run axe tests for the components below:
https://www.patternfly.org/components/menus/custom-menus/react-demos/application-launcher-menu/
https://www.patternfly.org/components/tabs/#with-help-action-popover

**Expected behavior**
A clear and concise description of the expected behavior.
No violations

user: jenny-s51
issue_9966: state: open
title: Bug - Tabs - uncontrolled Tabs do not react to updated defaultActiveKey
body: **Describe the problem**
If an uncontrolled `<Tabs/>` is wrapped in some enclosing component that chooses between two `<Tabs/>` based on some selection (e.g. show either Tabs1 or Tabs2 based on a user selection, where the set of tabs in each may be different), then `<Tabs/>` does not adjust to the new `defaultActiveKey`.

Say Tabs1 has tabs [A,B,C] and Tabs2 has tabs [B,C]. If the `defaultActiveKey` for Tabs1 is A and for Tabs2 is B... then when switching from showing Tabs1 to showing Tabs2, the patternfly `<Tabs/>` almost gets it right, but tab B in Tabs2 comes up with the `hidden` attribute, meaning that the displayed tab content is blank.

Note, if the selection chooses between two separate `<Tabs/>` things are fine. But if the selection uses a single `<Tabs/>` with different `[<Tab/>]` content, then something in the way `<Tabs/>` manages state does not work.

I suspect this is due to a missing getDerivedStateFromProps?

**How do you reproduce the problem?**
https://codesandbox.io/p/sandbox/jovial-lucy-jsjcr4

In that sandbox, click on "B" and note that the "Containers" tab shows no content. Then, switch back to "A" and then click on its "Containers" tab. Now when you switch to "B" the "Containers" tab content is shown.

**Expected behavior**
The Containers tab content should not be hidden.

**Is this issue blocking you?**
The only workaround I see is to use a `key=...` to force the `<Tabs/>` constructor to be re-evaluated.

**Screenshots**
n/a

**What is your environment?**
 - OS: any
 - Browser any
 - Version 5.1.1

**What is your product and what release date are you targeting?**

**Any other information?**

user: starpit
issue_9959: state: open
title: Update workspace to use latest version of yarn (not yarn v1)
body: New features in Yarn (or PNPM for that matter) is the workspace: protocol, which allows us to refer to workspace dependencies without needing to specify an exact version. This reduces the chances of merge conficts when these versions are bumped.

See:

- https://yarnpkg.com/features/workspaces#cross-references
- https://pnpm.io/workspaces#workspace-protocol-workspace
- https://lerna.js.org/docs/recipes/using-pnpm-with-lerna
- https://yarnpkg.com/getting-started/install#updating-yarn

(reported/suggested by @jonkoops who has offered to be a resource)
user: nicolethoen
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_9945: state: open
title: chore: Replace `lodash/uniqueId` with `getUniqueId()`
body: Replaces all usage of `lodash/uniqueId` with [`getUniqueId()`](https://github.com/patternfly/patternfly-react/blob/19ddee701efb222b931b83c531987405860d604f/packages/react-core/src/helpers/util.ts#L14-L17), reducing the dependency on Lodash as a whole.

Works towards closing #9942
user: jonkoops
issue_9944: state: open
title: chore: Replace `lodash/orderBy` with `Array.prototype.sort()`
body: Replaces all usage of `lodash/orderBy` with [`Array.prototype.sort()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort), reducing the dependency on Lodash as a whole.

Works towards closing #9942
user: jonkoops
issue_9942: state: open
title: Remove lodash dependency from charts + table
body: Lodash is no longer a supported library. (no new releases since 2016)

Some of these might be replaceable with built-in APIs depending on the browser support target. For example lodash/cloneDeep could be replaced with [structuredClone()](https://developer.mozilla.org/en-US/docs/Web/API/structuredClone).

It's only a dependency in charts + table right now.

user: nicolethoen
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_9936: state: open
title: Bug - Popper - Component crash when no children defined
body: The popper component is throwing an error (see screen grab and stack trace below)

Changing [https://github.com/openshift/console/blob/0ed60b588f0be2090f3bec5a6a4c4e67eb8dc1ef[…]ents/dropdown/dropdown-with-switch/DropdownWithSwitchToggle.tsx](https://github.com/openshift/console/blob/0ed60b588f0be2090f3bec5a6a4c4e67eb8dc1ef/frontend/packages/console-shared/src/components/dropdown/dropdown-with-switch/DropdownWithSwitchToggle.tsx#L50) to `popper={<>{menu}</>}` is a hack to workaround the issue.

In OCP's case, the Popper's `popper` prop is receiving a DropdownWithSwitchMenu component as a value which is of type `React.FC<DropdownWithSwitchMenuProps>`. This menu does not have a `children` prop, so the error is thrown, unless it's wrapped in a React fragment. Some sort of coercion of types is happening. Maybe the type of the `popper` prop needs to be tightened to prevent this run time error?

https://github.com/patternfly/patternfly-react/assets/26305082/87f8eac2-32b6-4b0a-b6bc-d56eb56cb3e3

![Screenshot 2024-01-02 at 11 14 48 AM](https://github.com/patternfly/patternfly-react/assets/26305082/262149d6-8b6e-4ae1-ac40-77354c7ac16d)


user: nicolethoen
issue_9935: state: open
title: docs: Code Editor - update header content example
body: "With shortcut menu and main header content" example for Code Editor does not actually pass any header content in, and should be updated to have content.
user: kmcfaul
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9933: state: open
title: Bug - Datepicker - End date validator lacks support for "isSameOrBefore" case
body: 
**Describe the problem**
The PatternFly DatePicker component exhibits unexpected behavior when using the `toValidator` function in a date range selection scenario. The issue arises when the validator condition checks if the end date is greater than the start date (`yyyy-MM-DD > yyyy-MM-DD`). This results in the selected styles for the end date range not being applied correctly.

**Affected Components**
- DatePicker

**How do you reproduce the problem?**
Steps to reproduce:
1. Set up a DatePicker component to select a date range.
2. Implement a `toValidator` function similar to this:
   ```javascript
   const toValidator = (date) => {
       return isValidDate(from) && yyyyMMddFormat(date) > yyyyMMddFormat(from)
         ? ''
         : 'The "to" date must be after the "from" date';
   };
   ```
3. Select a start date at the end of the month.
4. Open the end date datepicker and observe that the selected styles for the end date range are not applied.

You can reproduce this issue within the [PF datepicker demo example](https://www.patternfly.org/components/date-and-time/date-and-time-picker/#date-and-time-range-picker).

**Expected behavior**
The expected behavior is that when selecting a start date at the end of the month, the end date datepicker should show the correct beginning range with selected styles applied. 

**Is this issue blocking you?**
Not blocking. 

**Screenshots**
<img width="964" alt="Screenshot 2024-01-03 at 4 04 10 PM" src="https://github.com/patternfly/patternfly-react/assets/11218376/332d5037-b2e4-4c41-9999-c7fe98532b60">
<img width="890" alt="Screenshot 2024-01-03 at 4 05 50 PM" src="https://github.com/patternfly/patternfly-react/assets/11218376/c677fa85-599f-4b6c-98a2-61f6bb7c46f9">

**Environment**
- OS: [e.g. macOS]
- Browser: [e.g. Chrome]
- Version: [e.g. 90.0]

**Product and Release Date**
(Product details and intended release date for the feature using this component)

**Additional Information**
Upon changing the `toValidator` function condition from `>=` to `>`, the DatePicker component's end date range start selected styles do not apply as intended. It appears the PatternFly DatePicker requires an end date range that starts with the start date for proper functioning.



user: ibolton336
issue_9931: state: open
title: Consume core Penta updates: Form controls, checkbox, radio
body: Follow up to core issue https://github.com/patternfly/patternfly/issues/6156
user: tlabaj
issue_9927: state: open
title: Consume core updates: Breadcrumb ( Follow up to issue)
body: Follow up to core issue https://github.com/patternfly/patternfly/issues/5731

Also depend on core issue https://github.com/patternfly/patternfly/issues/6162 for menu styling 
user: tlabaj
issue_9925: state: open
title: Consume core Penta updates: Data list
body: Follow up to core issue https://github.com/patternfly/patternfly/issues/6106
user: tlabaj
issue_9923: state: open
title: Consume core updates: Notification Drawer ( Follow up to issue)
body: Follow up to core issue https://github.com/patternfly/patternfly/issues/5714
Also depend on core issue https://github.com/patternfly/patternfly/issues/6162 for menu styling
user: tlabaj
issue_9922: state: open
title: Bug - Button - loading spinner hard to see
body: **Describe the problem**
When the button is both disabled and in loading state, the loading spinner is hard to see. See comparison PF4 and PF5.

**How do you reproduce the problem?**
```
<Button variant="secondary" isLoading isDisabled>Secondary</Button>
```

**PF4**
https://github.com/patternfly/patternfly-react/assets/869106/f27800b7-0dfd-4fdf-a4f2-71986f283251

**PF5**
https://github.com/patternfly/patternfly-react/assets/869106/90dbd1d7-78ef-402d-ab8d-5c1a3489211a


**What is your environment?**
 - OS: macOS
 - Browser: Firefox
 - Version: 115.6.0esr (64-bit)

**What is your product and what release date are you targeting?**
OCM

**Any other information?**

user: jschuler
issue_9906: state: open
title: AlertGroupProvider - Provide A Cleaner Method of Dispatching Alerts.
body: **Is this a new component or an extension of an existing one?**
This would technically be a couple of new components and a new hook. For all intents and purposes though this would just be a thin wrapper around the existing `AlertGroup`, `Alert`, and `AlertActionCloseButton` component though.

**Describe the feature**
This new feature would make it easier for users to dispatch alerts from their applications. Essentially my idea is that there should be an `AlertGroupProvider` that tracks and displays alerts. This `AlertGroupProvider` would set a dispatch function for a Patternfly private `AlertContext`. This would allow for a new `useDispatchAlert` hook to be created that returns the dispatch function for the Patternfly private `AlertContext`.

**Are there visuals for this feature? If applicable, please include examples for each state and for varying widths**
There aren't any new visuals for this proposed feature.

**Example of proposed use**
```typescript
import React from "react";
import { createRoot } from "react-dom/client";
import { AlertGroupProvider, useDispatchAlert } from "@patternfly/react-core";
import "@patternfly/patternfly/patternfly.css";
import "@patternfly/react-core/dist/styles/base.css";
import ToastAlertProvider from "./app/components/providers/ToastAlertProvider";

const ID = "root";
const container = document.getElementById(ID);
if (container === null) {
  throw new Error(`No element with ID ${ID} found`);
}
const root = createRoot(container);
const router = createBrowserRouter(routes);

root.render(
  <React.StrictMode>
    <AlertGroupProvider>
      <App />
    </AlertGroupProvider>
  </React.StrictMode>,
);

function App() {
  const dispatchAlert = useDispatchAlert();
  React.useEffect(() => {
    dispatchAlert({
      title: "Info",
      content: "This is a test alert",
    });
  }, [dispatchAlert]);
  return (
    <p>Example application</p>
  );
}
```

**Uncertainties that I have about this proposed enhancement**
I am currently using a pattern like this to dispatch toasts in an application that I am maintaining so I know that it's doable. What I am not sure about is whether or not this is something that should be done within Patternfly or if it would require enough assumptions that it would be best to leave to application maintainers as is currently being done.
user: lannuttia
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9905: state: open
title: [Switch] - [add hasCheckIcon implementation to switch with no label]
body: **Is this a new component or an extension of an existing one?**
Switch

**Describe the feature**
add hasCheckIcon implementation to Switch with no label to hide the CheckIcon based on user input

**Are there visuals for this feature? If applicable, please include examples for each state and for varying widths**
No

**Any other information?**
https://github.com/patternfly/patternfly-react/pull/9904

user: yamalameyooooo
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_9904: state: open
title: Added hasCheckIcon implementation to switch with no label to hide the CheckIcon based on user input
body: https://github.com/patternfly/patternfly-react/issues/9905

Added hasCheckIcon implementation to switch with no label to hide the CheckIcon based on user input
user: yamalameyooooo
issue_9902: state: open
title: Bug - Table - Examples using wrong type for sorts
body: Several table examples are using `number | null` for sortIndex and `'asc' | 'desc' | null` for sortDirection while the sortBy object wants `undefined` instead of `null`.

Came up in this discussion: https://patternfly.slack.com/archives/C4FM977N0/p1703294961208719?thread_ts=1703237597.944969&cid=C4FM977N0
user: gitdallas
issue_9900: state: open
title: Bug - Dual List Selector - Formatting doesn't update when an item containing `<TextContent>` gets disabled
body: We have recently migrated from PatternFly 4 to PatternFly 5 and noticed a following problem.

Formatting for a `<DualListSelectorItem>` which contains `<TextContent>` doesn't update when the item gets disabled. The item gets assigned `.pf-m-disabled` correctly and is no longer clickable, but does not get greyed out.

See "vim-common" on the screenshot - we want to keep the item in the list of available packages on the left even when it's added to chosen, but disable it).

![Screenshot from 2023-12-20 10-49-16](https://github.com/patternfly/patternfly-react/assets/49452678/e438e32e-3d95-4e76-ba36-95b62c1cae23)

The item has following structure:
```javascript
  <DualListSelectorListItem
    data-testid={`available-pkgs-${pkg.name}`}
    key={pkg.name}
    isDisabled={chosenPackages[pkg.name] ? true : false}
    isSelected={selectedAvailablePackages.has(pkg.name)}
    onOptionSelect={(e) => handleSelectAvailable(e, pkg.name)}
  >
    <TextContent key={`${pkg.name}`}>
      <span className="pf-c-dual-list-selector__item-text">
        {pkg.name}
      </span>
      <small>{pkg.summary}</small>
    </TextContent>
  </DualListSelectorListItem>
```

The formatting used to be applied like this in PatternFly 4 for the exactly same case:

![Screenshot from 2023-12-20 10-47-47](https://github.com/patternfly/patternfly-react/assets/49452678/976c8030-4ca5-48cd-815d-4b6289e18fd6)

Possible workaround is replacing the `<TextContent>` with plain `<div>` like so:

![image](https://github.com/patternfly/patternfly-react/assets/49452678/d58d6e41-136d-4c74-ae11-fa935c411638)

The formatting for a disabled item gets applied correctly then, but we'd like to keep using the item with `<TextContent>` if possible.
user: regexowl
issue_9898: state: open
title: chore(deps): update devdependencies (major)
body: [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [@testing-library/jest-dom](https://togithub.com/testing-library/jest-dom) | [`^5.16.5` -> `^6.0.0`](https://renovatebot.com/diffs/npm/@testing-library%2fjest-dom/5.17.0/6.4.2) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@testing-library%2fjest-dom/6.4.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@testing-library%2fjest-dom/6.4.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@testing-library%2fjest-dom/5.17.0/6.4.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@testing-library%2fjest-dom/5.17.0/6.4.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/typescript-eslint) ([source](https://togithub.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin)) | [`^5.59.2` -> `^7.0.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2feslint-plugin/5.62.0/7.0.1) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@typescript-eslint%2feslint-plugin/7.0.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@typescript-eslint%2feslint-plugin/7.0.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@typescript-eslint%2feslint-plugin/5.62.0/7.0.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@typescript-eslint%2feslint-plugin/5.62.0/7.0.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@typescript-eslint/parser](https://togithub.com/typescript-eslint/typescript-eslint) ([source](https://togithub.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser)) | [`^5.59.2` -> `^7.0.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2fparser/5.62.0/7.0.1) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@typescript-eslint%2fparser/7.0.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@typescript-eslint%2fparser/7.0.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@typescript-eslint%2fparser/5.62.0/7.0.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@typescript-eslint%2fparser/5.62.0/7.0.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [lint-staged](https://togithub.com/okonet/lint-staged) | [`^14.0.0` -> `^15.0.0`](https://renovatebot.com/diffs/npm/lint-staged/14.0.1/15.2.2) | [![age](https://developer.mend.io/api/mc/badges/age/npm/lint-staged/15.2.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/lint-staged/15.2.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/lint-staged/14.0.1/15.2.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/lint-staged/14.0.1/15.2.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [plop](https://plopjs.com) ([source](https://togithub.com/plopjs/plop/tree/HEAD/packages/plop)) | [`^3.1.2` -> `^4.0.0`](https://renovatebot.com/diffs/npm/plop/3.1.2/4.0.1) | [![age](https://developer.mend.io/api/mc/badges/age/npm/plop/4.0.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/plop/4.0.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/plop/3.1.2/4.0.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/plop/3.1.2/4.0.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [rollup](https://rollupjs.org/) ([source](https://togithub.com/rollup/rollup)) | [`^3.21.5` -> `^4.0.0`](https://renovatebot.com/diffs/npm/rollup/3.29.4/4.10.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/rollup/4.10.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/rollup/4.10.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/rollup/3.29.4/4.10.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/rollup/3.29.4/4.10.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [ts-patch](https://togithub.com/nonara/ts-patch) | [`^2.1.0` -> `^3.0.0`](https://renovatebot.com/diffs/npm/ts-patch/2.1.0/3.1.2) | [![age](https://developer.mend.io/api/mc/badges/age/npm/ts-patch/3.1.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/ts-patch/3.1.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/ts-patch/2.1.0/3.1.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/ts-patch/2.1.0/3.1.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) |

---

### Release Notes

<details>
<summary>testing-library/jest-dom (@&#8203;testing-library/jest-dom)</summary>

### [`v6.4.2`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.4.2)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.4.1...v6.4.2)

##### Bug Fixes

-   Remove errant export of GetByRoleMatcher, fixing type checking in some TS configurations ([#&#8203;575](https://togithub.com/testing-library/jest-dom/issues/575)) ([a93c0c4](https://togithub.com/testing-library/jest-dom/commit/a93c0c4a20ed4d3a9656261ea6a449d1015b7879))

### [`v6.4.1`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.4.1)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.4.0...v6.4.1)

##### Bug Fixes

-   Export type `TestingLibraryMatchers` from "./matchers" ([#&#8203;576](https://togithub.com/testing-library/jest-dom/issues/576)) ([dd1c4dd](https://togithub.com/testing-library/jest-dom/commit/dd1c4dd504973efced2f9e02a35e7df3079914af))

### [`v6.4.0`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.4.0)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.3.0...v6.4.0)

##### Features

-   Add toHaveRole matcher ([#&#8203;572](https://togithub.com/testing-library/jest-dom/issues/572)) ([f7dc673](https://togithub.com/testing-library/jest-dom/commit/f7dc673dbc13e508f9867a9eb9c547ce3964b22c))

### [`v6.3.0`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.3.0)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.2.1...v6.3.0)

##### Features

-   Support for regular expressions in toHaveClass ([#&#8203;563](https://togithub.com/testing-library/jest-dom/issues/563)) ([9787ed5](https://togithub.com/testing-library/jest-dom/commit/9787ed59fcc930e3d33c8a6efe473da3eca01707))

### [`v6.2.1`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.2.1)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.2.0...v6.2.1)

##### Bug Fixes

-   Standalone types for "./matchers" export and add Bun support ([#&#8203;566](https://togithub.com/testing-library/jest-dom/issues/566)) ([5675b86](https://togithub.com/testing-library/jest-dom/commit/5675b8668c09345e064001784338a85b7bf9f2af))

### [`v6.2.0`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.2.0)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.1.6...v6.2.0)

##### Features

-   toHaveAccessibleDescription supports aria-description ([#&#8203;565](https://togithub.com/testing-library/jest-dom/issues/565)) ([1fb156c](https://togithub.com/testing-library/jest-dom/commit/1fb156c2b544e0069c56a72a2f1909fe04850f6c))

### [`v6.1.6`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.1.6)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.1.5...v6.1.6)

##### Bug Fixes

-   Upgrade [@&#8203;adobe/css-tools](https://togithub.com/adobe/css-tools) to v4.3.2 ([#&#8203;553](https://togithub.com/testing-library/jest-dom/issues/553)) ([b64b953](https://togithub.com/testing-library/jest-dom/commit/b64b953f76170f282c73329ee3479ede13610713))

### [`v6.1.5`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.1.5)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.1.4...v6.1.5)

##### Bug Fixes

-   support uppercase custom props in toHaveStyle ([#&#8203;552](https://togithub.com/testing-library/jest-dom/issues/552)) ([b7b7c6a](https://togithub.com/testing-library/jest-dom/commit/b7b7c6a9652f259434d13a22e4319826a4bd4d8b))

### [`v6.1.4`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.1.4)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.1.3...v6.1.4)

##### Bug Fixes

-   upgrade `@adobe/css-tools` to `4.3.1` to address vulnerability ([#&#8203;532](https://togithub.com/testing-library/jest-dom/issues/532)) ([44f1eab](https://togithub.com/testing-library/jest-dom/commit/44f1eabc79b848f45daffac21c5f7383424e893c))

### [`v6.1.3`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.1.3)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.1.2...v6.1.3)

##### Bug Fixes

-   proper [@&#8203;jest/globals](https://togithub.com/jest/globals) import ([#&#8203;530](https://togithub.com/testing-library/jest-dom/issues/530)) ([5b492ac](https://togithub.com/testing-library/jest-dom/commit/5b492ace23d52b7cb7d3f91913ed0b5311905a26))

### [`v6.1.2`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.1.2)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.1.1...v6.1.2)

##### Bug Fixes

-   bump [@&#8203;adobe/css-tools](https://togithub.com/adobe/css-tools) for ESM support ([#&#8203;525](https://togithub.com/testing-library/jest-dom/issues/525)) ([b959a68](https://togithub.com/testing-library/jest-dom/commit/b959a681386164bf5d64f5b2b9c8bf891301bc12))

### [`v6.1.1`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.1.1)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.1.0...v6.1.1)

##### Bug Fixes

-   **package.json:** update main and module file paths ([#&#8203;523](https://togithub.com/testing-library/jest-dom/issues/523)) ([853a3e5](https://togithub.com/testing-library/jest-dom/commit/853a3e51ba6757a34780e32953525b6142eadcf9))

### [`v6.1.0`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.1.0)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.0.1...v6.1.0)

##### Features

-   Publish ESM and CJS ([https://github.com/testing-library/jest-dom/pull/519](https://togithub.com/testing-library/jest-dom/pull/519))

### [`v6.0.1`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.0.1)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v6.0.0...v6.0.1)

##### Bug Fixes

-   matchers type is making the global expect unsafe ([#&#8203;513](https://togithub.com/testing-library/jest-dom/issues/513)) ([bdb34f1](https://togithub.com/testing-library/jest-dom/commit/bdb34f12959578c77b18b0c0910d512768b20ab0))

### [`v6.0.0`](https://togithub.com/testing-library/jest-dom/releases/tag/v6.0.0)

[Compare Source](https://togithub.com/testing-library/jest-dom/compare/v5.17.0...v6.0.0)

##### Features

-   local types, supporting jest, [@&#8203;jest/globals](https://togithub.com/jest/globals), vitest ([#&#8203;511](https://togithub.com/testing-library/jest-dom/issues/511)) ([4b764b9](https://togithub.com/testing-library/jest-dom/commit/4b764b9f6a7b564d7f8ec0e9b0c6ba9cc875f2b8))

##### BREAKING CHANGES

-   Removes the extend-expect script. Users should use
    the default import path or one of the new test platform-specific
    paths to automatically extend the appropriate "expect" instance.

extend-expect was not documented in the Readme, so this change should
have minimal impact.

Users can now use the following import paths to automatically extend
"expect" for their chosen test platform:

-   [@&#8203;testing-library/jest-dom](https://togithub.com/testing-library/jest-dom) - jest ([@&#8203;types/jest](https://togithub.com/types/jest))
-   @&#8203;testing-library/jest-dom/jest-globals - [@&#8203;jest/globals](https://togithub.com/jest/globals)
-   @&#8203;testing-library/jest-dom/vitest - vitest

For example:

import '@&#8203;testing-library/jest-dom/jest-globals'

Importing from one of the above paths will augment the appropriate
matcher interface for the given test platform, assuming the import
is done in a .ts file that is included in the user's tsconfig.json.

It's also (still) possible to import the matchers directly without
side effects:

import \* as matchers from '@&#8203;testing-library/jest-dom/matchers'

-   Update kcd-scripts
-   Drop node < 14

</details>

<details>
<summary>typescript-eslint/typescript-eslint (@&#8203;typescript-eslint/eslint-plugin)</summary>

### [`v7.0.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#701-2024-02-12)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v7.0.0...v7.0.1)

##### 🩹 Fixes

-   **eslint-plugin:** update peer dep for parser

##### ❤️  Thank You

-   Tim Dorr

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v7.0.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#700-2024-02-12)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.21.0...v7.0.0)

##### 🚀 Features

-   ⚠️  bump ESLint, NodeJS, and TS minimum version requirements

-   add support for flat configs

##### 🩹 Fixes

-   **eslint-plugin:** \[prefer-find] stop throwing type errors when converting symbols to numbers

##### ⚠️  Breaking Changes

-   ⚠️  bump ESLint, NodeJS, and TS minimum version requirements

##### ❤️  Thank You

-   Brad Zacher
-   Kirk Waiblinger
-   StyleShit
-   YeonJuan

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### 6.21.0 (2024-02-05)

##### 🚀 Features

-   export plugin metadata

-   allow `parserOptions.project: false`

-   **eslint-plugin:** add rule prefer-find

##### 🩹 Fixes

-   **eslint-plugin:** \[no-unused-vars] don't report on types referenced in export assignment expression

-   **eslint-plugin:** \[switch-exhaustiveness-check] better support for intersections, infinite types, non-union values

-   **eslint-plugin:** \[consistent-type-imports] dont report on types used in export assignment expressions

-   **eslint-plugin:** \[no-unnecessary-condition] handle left-hand optional with exactOptionalPropertyTypes option

-   **eslint-plugin:** \[class-literal-property-style] allow getter when same key setter exists

-   **eslint-plugin:** \[no-unnecessary-type-assertion] provide valid fixes for assertions with extra tokens before `as` keyword

##### ❤️  Thank You

-   auvred
-   Brad Zacher
-   Kirk Waiblinger
-   Pete Gonzalez
-   YeonJuan

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### 6.20.0 (2024-01-29)

##### 🚀 Features

-   **eslint-plugin:** \[member-ordering] allow easy reuse of the default ordering

##### 🩹 Fixes

-   **eslint-plugin:** \[no-useless-template-literals] incorrect bigint autofix result

-   **eslint-plugin:** \[prefer-nullish-coalescing] treat any/unknown as non-nullable

-   **eslint-plugin:** \[no-useless-template-literals] report Infinity & NaN

-   **eslint-plugin:** \[prefer-readonly] disable checking accessors

##### ❤️  Thank You

-   Alex Parloti
-   auvred
-   James Browning
-   StyleShit
-   YeonJuan

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### 6.19.1 (2024-01-22)

##### 🩹 Fixes

-   **type-utils:** preventing isUnsafeAssignment infinite recursive calls

-   **eslint-plugin:** \[no-unnecessary-condition] fix false positive for type variable

##### ❤️  Thank You

-   YeonJuan

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### 6.19.0 (2024-01-15)

##### 🚀 Features

-   **eslint-plugin:** \[prefer-promise-reject-errors] add rule

-   **eslint-plugin:** \[no-array-delete] add new rule

-   **eslint-plugin:** \[no-useless-template-literals] add fix suggestions

##### 🩹 Fixes

-   **eslint-plugin:** \[no-unnecessary-type-assertion] detect unnecessary non-null-assertion on a call expression

-   **eslint-plugin:** \[no-unnecesary-type-assertion] treat unknown/any as nullable

##### ❤️  Thank You

-   auvred
-   Brad Zacher
-   Josh Goldberg ✨
-   Joshua Chen
-   LJX
-   Steven
-   StyleShit

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### 6.18.1 (2024-01-08)

##### 🩹 Fixes

-   **eslint-plugin:** \[no-non-null-assertion] provide valid fix when member access is on next line

-   **eslint-plugin:** \[no-unnecessary-condition] improve checking optional callee

-   **eslint-plugin:** \[prefer-readonly] support modifiers of unions and intersections

-   **eslint-plugin:** \[switch-exhaustiveness-check] fix new allowDefaultCaseForExhaustiveSwitch option

##### ❤️  Thank You

-   auvred
-   James
-   Josh Goldberg ✨
-   YeonJuan

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### 6.18.0 (2024-01-06)

##### 🚀 Features

-   **typescript-estree:** throw on invalid update expressions

-   **eslint-plugin:** \[no-var-requires, no-require-imports] allow option

##### ❤️  Thank You

-   auvred
-   Joshua Chen

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.21.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6210-2024-02-05)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.20.0...v6.21.0)

##### 🚀 Features

-   export plugin metadata

-   allow `parserOptions.project: false`

-   **eslint-plugin:** add rule prefer-find

##### 🩹 Fixes

-   **eslint-plugin:** \[no-unused-vars] don't report on types referenced in export assignment expression

-   **eslint-plugin:** \[switch-exhaustiveness-check] better support for intersections, infinite types, non-union values

-   **eslint-plugin:** \[consistent-type-imports] dont report on types used in export assignment expressions

-   **eslint-plugin:** \[no-unnecessary-condition] handle left-hand optional with exactOptionalPropertyTypes option

-   **eslint-plugin:** \[class-literal-property-style] allow getter when same key setter exists

-   **eslint-plugin:** \[no-unnecessary-type-assertion] provide valid fixes for assertions with extra tokens before `as` keyword

##### ❤️  Thank You

-   auvred
-   Brad Zacher
-   Kirk Waiblinger
-   Pete Gonzalez
-   YeonJuan

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.20.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6200-2024-01-29)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.19.1...v6.20.0)

##### 🚀 Features

-   **eslint-plugin:** \[member-ordering] allow easy reuse of the default ordering

##### 🩹 Fixes

-   **eslint-plugin:** \[no-useless-template-literals] incorrect bigint autofix result

-   **eslint-plugin:** \[prefer-nullish-coalescing] treat any/unknown as non-nullable

-   **eslint-plugin:** \[no-useless-template-literals] report Infinity & NaN

-   **eslint-plugin:** \[prefer-readonly] disable checking accessors

##### ❤️  Thank You

-   Alex Parloti
-   auvred
-   James Browning
-   StyleShit
-   YeonJuan

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.19.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6191-2024-01-22)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.19.0...v6.19.1)

##### 🩹 Fixes

-   **type-utils:** preventing isUnsafeAssignment infinite recursive calls

-   **eslint-plugin:** \[no-unnecessary-condition] fix false positive for type variable

##### ❤️  Thank You

-   YeonJuan

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.19.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6190-2024-01-15)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.18.1...v6.19.0)

##### 🚀 Features

-   **eslint-plugin:** \[prefer-promise-reject-errors] add rule

-   **eslint-plugin:** \[no-array-delete] add new rule

-   **eslint-plugin:** \[no-useless-template-literals] add fix suggestions

##### 🩹 Fixes

-   **eslint-plugin:** \[no-unnecessary-type-assertion] detect unnecessary non-null-assertion on a call expression

-   **eslint-plugin:** \[no-unnecesary-type-assertion] treat unknown/any as nullable

##### ❤️  Thank You

-   auvred
-   Brad Zacher
-   Josh Goldberg ✨
-   Joshua Chen
-   LJX
-   Steven
-   StyleShit

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.18.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6181-2024-01-08)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.18.0...v6.18.1)

##### 🩹 Fixes

-   **eslint-plugin:** \[no-non-null-assertion] provide valid fix when member access is on next line

-   **eslint-plugin:** \[no-unnecessary-condition] improve checking optional callee

-   **eslint-plugin:** \[prefer-readonly] support modifiers of unions and intersections

-   **eslint-plugin:** \[switch-exhaustiveness-check] fix new allowDefaultCaseForExhaustiveSwitch option

##### ❤️  Thank You

-   auvred
-   James
-   Josh Goldberg ✨
-   YeonJuan

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.18.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6180-2024-01-06)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.17.0...v6.18.0)

##### 🚀 Features

-   **typescript-estree:** throw on invalid update expressions

-   **eslint-plugin:** \[no-var-requires, no-require-imports] allow option

##### ❤️  Thank You

-   auvred
-   Joshua Chen

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.17.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6170-2024-01-01)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.16.0...v6.17.0)

##### Bug Fixes

-   **eslint-plugin:** \[no-restricted-imports] prevent crash when `patterns` or `paths` in options are empty ([#&#8203;8108](https://togithub.com/typescript-eslint/typescript-eslint/issues/8108)) ([675e987](https://togithub.com/typescript-eslint/typescript-eslint/commit/675e987ca1d13244c03d7e09d4e42c6539689d9a))

##### Features

-   **eslint-plugin:** \[no-floating-promises] flag result of .map(async) ([#&#8203;7897](https://togithub.com/typescript-eslint/typescript-eslint/issues/7897)) ([5857356](https://togithub.com/typescript-eslint/typescript-eslint/commit/5857356962060b19aa792bee778f9167ee54154b))
-   **eslint-plugin:** \[switch-exhaustiveness-check] add an option to warn against a `default` case on an already exhaustive `switch` ([#&#8203;7539](https://togithub.com/typescript-eslint/typescript-eslint/issues/7539)) ([6a219bd](https://togithub.com/typescript-eslint/typescript-eslint/commit/6a219bdfe6fcf86aae28158e0d855f87a8bac719))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.16.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6160-2023-12-25)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.15.0...v6.16.0)

##### Bug Fixes

-   **eslint-plugin:** \[unbound-method] exempt all non-Promise built-in statics ([#&#8203;8096](https://togithub.com/typescript-eslint/typescript-eslint/issues/8096)) ([3182959](https://togithub.com/typescript-eslint/typescript-eslint/commit/31829591e2c5cf6bdbdd5da23b12c5782f710fa5))

##### Features

-   **eslint-plugin:** deprecate formatting (meta.type: layout) rules ([#&#8203;8073](https://togithub.com/typescript-eslint/typescript-eslint/issues/8073)) ([04dea84](https://togithub.com/typescript-eslint/typescript-eslint/commit/04dea84e8e934a415ec1381a90de3cde670d0dc3))
-   **eslint-plugin:** deprecate no-extra-semi in favor of ESLint Stylistic equivalent ([#&#8203;8123](https://togithub.com/typescript-eslint/typescript-eslint/issues/8123)) ([9368bf3](https://togithub.com/typescript-eslint/typescript-eslint/commit/9368bf390afc58a19123782f8dff2bb5cdd3cccc))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.15.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6150-2023-12-18)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.14.0...v6.15.0)

##### Features

-   **eslint-plugin:** \[no-useless-template-literals] add new rule ([#&#8203;7957](https://togithub.com/typescript-eslint/typescript-eslint/issues/7957)) ([ff75785](https://togithub.com/typescript-eslint/typescript-eslint/commit/ff75785f4c6cc41999f8ce946bfca469d6e40e50)), closes [#&#8203;2846](https://togithub.com/typescript-eslint/typescript-eslint/issues/2846)
-   require-array-sort-compare + toSorted ([#&#8203;8052](https://togithub.com/typescript-eslint/typescript-eslint/issues/8052)) ([c9661c8](https://togithub.com/typescript-eslint/typescript-eslint/commit/c9661c8bbf048e9fa3ef55985e1e2e82bc098b1a))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.14.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6140-2023-12-11)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.13.2...v6.14.0)

##### Bug Fixes

-   **eslint-plugin:** add no-unsafe-unary-minus, prefer-destructuring to disable-type-checked ([#&#8203;8038](https://togithub.com/typescript-eslint/typescript-eslint/issues/8038)) ([431cd15](https://togithub.com/typescript-eslint/typescript-eslint/commit/431cd1559f91795e958e03fd060ceaf79fb96f3a))
-   **eslint-plugin:** correct message for `no-unsafe-unary-minus` ([#&#8203;7998](https://togithub.com/typescript-eslint/typescript-eslint/issues/7998)) ([705370a](https://togithub.com/typescript-eslint/typescript-eslint/commit/705370ac0d9c54081657b8855b398e57d6ea4ddb))

##### Features

-   **eslint-plugin:** \[explicit-function-return-type] add support for typed class property definitions ([#&#8203;8027](https://togithub.com/typescript-eslint/typescript-eslint/issues/8027)) ([bff47d7](https://togithub.com/typescript-eslint/typescript-eslint/commit/bff47d7885bee3bbcb3a81eff273fe2f48580940))
-   **eslint-plugin:** \[require-await] allow yielding Promise in async generators ([#&#8203;8003](https://togithub.com/typescript-eslint/typescript-eslint/issues/8003)) ([4c3e704](https://togithub.com/typescript-eslint/typescript-eslint/commit/4c3e704b97e698df7f72174c2d20714836d4d243))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### [6.13.2](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.13.1...v6.13.2) (2023-12-04)

**Note:** Version bump only for package [@&#8203;typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### [6.13.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.13.0...v6.13.1) (2023-11-28)

**Note:** Version bump only for package [@&#8203;typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.13.2`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6132-2023-12-04)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.13.1...v6.13.2)

**Note:** Version bump only for package [@&#8203;typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.13.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6131-2023-11-28)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.13.0...v6.13.1)

**Note:** Version bump only for package [@&#8203;typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.13.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6130-2023-11-27)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.12.0...v6.13.0)

**Note:** Version bump only for package [@&#8203;typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.12.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6120-2023-11-20)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.11.0...v6.12.0)

##### Bug Fixes

-   **eslint-plugin:** \[class-methods-use-this] detect a problematic case for private/protected members if `ignoreClassesThatImplementAnInterface` is set ([#&#8203;7705](https://togithub.com/typescript-eslint/typescript-eslint/issues/7705)) ([155aa1f](https://togithub.com/typescript-eslint/typescript-eslint/commit/155aa1f533d1fe23da3c66f9832343faf4866d85))
-   **eslint-plugin:** \[no-unnecessary-condition] fix false positive with computed member access and branded key type ([#&#8203;7706](https://togithub.com/typescript-eslint/typescript-eslint/issues/7706)) ([f151b26](https://togithub.com/typescript-eslint/typescript-eslint/commit/f151b26d2178a617e82ad6a0279e3145e303f4f8))
-   **eslint-plugin:** \[switch-exhaustiveness-check] enum members with new line or single quotes are not being fixed correctly ([#&#8203;7806](https://togithub.com/typescript-eslint/typescript-eslint/issues/7806)) ([a034d0a](https://togithub.com/typescript-eslint/typescript-eslint/commit/a034d0a3856aa07bd2d52b557fa33c7a88e9e511)), closes [#&#8203;7768](https://togithub.com/typescript-eslint/typescript-eslint/issues/7768)

##### Features

-   \[member-ordering] add accessor support for member-ordering ([#&#8203;7927](https://togithub.com/typescript-eslint/typescript-eslint/issues/7927)) ([3c8312d](https://togithub.com/typescript-eslint/typescript-eslint/commit/3c8312d1e135dc65fa41f629993cd03ed82e3255))
-   **eslint-plugin:** \[switch-exhaustiveness-check] add requireDefaultForNonUnion option ([#&#8203;7880](https://togithub.com/typescript-eslint/typescript-eslint/issues/7880)) ([4cfcd45](https://togithub.com/typescript-eslint/typescript-eslint/commit/4cfcd451efb2563130896e42b45252909932c679))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.11.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6110-2023-11-13)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.10.0...v6.11.0)

##### Bug Fixes

-   **eslint-plugin:** \[explicit-function-return-type] support JSX attributes in `allowTypedFunctionExpressions` ([#&#8203;7553](https://togithub.com/typescript-eslint/typescript-eslint/issues/7553)) ([be2777c](https://togithub.com/typescript-eslint/typescript-eslint/commit/be2777c5338669836d786f9a7806f499fd566dcd))
-   **eslint-plugin:** \[no-unnecessary-qualifier] handle nested namespace id ([#&#8203;7883](https://togithub.com/typescript-eslint/typescript-eslint/issues/7883)) ([a668f5b](https://togithub.com/typescript-eslint/typescript-eslint/commit/a668f5b10e7b1570c732312ad9ccab3431459c1b))

##### Features

-   add `no-unsafe-unary-minus` rule ([#&#8203;7390](https://togithub.com/typescript-eslint/typescript-eslint/issues/7390)) ([c4709c2](https://togithub.com/typescript-eslint/typescript-eslint/commit/c4709c2861f8ea4e18c289218a75224d6bb76193))
-   add types for flat config files ([#&#8203;7273](https://togithub.com/typescript-eslint/typescript-eslint/issues/7273)) ([66cd0c0](https://togithub.com/typescript-eslint/typescript-eslint/commit/66cd0c0535e5de1b46ba337919a9a92748d2b0a6))
-   allow typescript@5.3.0-RC as devDependency ([#&#8203;7821](https://togithub.com/typescript-eslint/typescript-eslint/issues/7821)) ([b6c40b4](https://togithub.com/typescript-eslint/typescript-eslint/commit/b6c40b42b68d5567c7468030ee45b9b84bec4c4d))
-   **eslint-plugin:** no-unsafe-enum-comparison handles switch cases ([#&#8203;7898](https://togithub.com/typescript-eslint/typescript-eslint/issues/7898)) ([72cb9e4](https://togithub.com/typescript-eslint/typescript-eslint/commit/72cb9e4ed397d35a8d8838d27dedbace6122179c))
-   **utils:** add ESLint `CodePath` selector types ([#&#8203;7551](https://togithub.com/typescript-eslint/typescript-eslint/issues/7551)) ([99a026f](https://togithub.com/typescript-eslint/typescript-eslint/commit/99a026fe41b4b169914352fe66e7d5d687b300bf))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.10.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#6100-2023-11-06)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.9.1...v6.10.0)

##### Bug Fixes

-   **eslint-plugin:** \[no-unused-vars] handle logical assignment ([#&#8203;7854](https://togithub.com/typescript-eslint/typescript-eslint/issues/7854)) ([11e57c5](https://togithub.com/typescript-eslint/typescript-eslint/commit/11e57c5937cc2ad2e6b035f8d3fb25a918490960))
-   **eslint-plugin:** \[require-await] add support for "await using" ([#&#8203;7866](https://togithub.com/typescript-eslint/typescript-eslint/issues/7866)) ([855abea](https://togithub.com/typescript-eslint/typescript-eslint/commit/855abea2d7ba0235e61430f9481117af5f8f1bf7))

##### Features

-   **eslint-plugin:** \[ban-ts-comments] suggest ts-expect-error over ts-ignore ([#&#8203;7849](https://togithub.com/typescript-eslint/typescript-eslint/issues/7849)) ([5e73a48](https://togithub.com/typescript-eslint/typescript-eslint/commit/5e73a4810add09470426129bc6b267cfaa42c378))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### [6.9.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.9.0...v6.9.1) (2023-10-30)

##### Bug Fixes

-   **eslint-plugin:** \[naming-convention] allow PascalCase for imports ([#&#8203;7841](https://togithub.com/typescript-eslint/typescript-eslint/issues/7841)) ([7ad86ee](https://togithub.com/typescript-eslint/typescript-eslint/commit/7ad86eead76fa9e96573ac011376c1cb8c009cee))
-   **eslint-plugin:** \[no-unused-expressions] handle TSInstantiationExpression expression ([#&#8203;7831](https://togithub.com/typescript-eslint/typescript-eslint/issues/7831)) ([31988e0](https://togithub.com/typescript-eslint/typescript-eslint/commit/31988e0d2e6cf5e6bb9bb287958b1f03ca084259))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.9.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#691-2023-10-30)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.9.0...v6.9.1)

##### Bug Fixes

-   **eslint-plugin:** \[naming-convention] allow PascalCase for imports ([#&#8203;7841](https://togithub.com/typescript-eslint/typescript-eslint/issues/7841)) ([7ad86ee](https://togithub.com/typescript-eslint/typescript-eslint/commit/7ad86eead76fa9e96573ac011376c1cb8c009cee))
-   **eslint-plugin:** \[no-unused-expressions] handle TSInstantiationExpression expression ([#&#8203;7831](https://togithub.com/typescript-eslint/typescript-eslint/issues/7831)) ([31988e0](https://togithub.com/typescript-eslint/typescript-eslint/commit/31988e0d2e6cf5e6bb9bb287958b1f03ca084259))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.9.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#690-2023-10-23)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.8.0...v6.9.0)

##### Bug Fixes

-   **eslint-plugin:** \[no-confusing-void-expression] handle unfixable cases ([#&#8203;7674](https://togithub.com/typescript-eslint/typescript-eslint/issues/7674)) ([7e52f27](https://togithub.com/typescript-eslint/typescript-eslint/commit/7e52f276ed5b8b2c0b76be02cb2e8a77892c10f2))
-   **eslint-plugin:** \[no-unsafe-return] allow returning anything if explicitly returning any ([#&#8203;7708](https://togithub.com/typescript-eslint/typescript-eslint/issues/7708)) ([c6124b2](https://togithub.com/typescript-eslint/typescript-eslint/commit/c6124b2c93a53f11471cce8054388dec7a58f90b))

##### Features

-   **eslint-plugin:** \[max-params] don't count `this: void` parameter ([#&#8203;7696](https://togithub.com/typescript-eslint/typescript-eslint/issues/7696)) ([6398d3f](https://togithub.com/typescript-eslint/typescript-eslint/commit/6398d3fd0a576d8cdc957ec1b57929acacc60ba0)), closes [#&#8203;7538](https://togithub.com/typescript-eslint/typescript-eslint/issues/7538)
-   **eslint-plugin:** \[naming-convention] add support for default and namespace imports ([#&#8203;7269](https://togithub.com/typescript-eslint/typescript-eslint/issues/7269)) ([bb15aae](https://togithub.com/typescript-eslint/typescript-eslint/commit/bb15aae877ae260f59aa5e6cfc338b1eefc6d85c))
-   **eslint-plugin:** \[no-restricted-imports] support import = require ([#&#8203;7709](https://togithub.com/typescript-eslint/typescript-eslint/issues/7709)) ([4c8edcf](https://togithub.com/typescript-eslint/typescript-eslint/commit/4c8edcfb7d3cc02d07d2329c87da4377c1cbf969))
-   **eslint-plugin:** \[no-unsafe-enum-comparison] add switch suggestion ([#&#8203;7691](https://togithub.com/typescript-eslint/typescript-eslint/issues/7691)) ([53d5263](https://togithub.com/typescript-eslint/typescript-eslint/commit/53d5263cee8e0b5ddc5de3321d27559c196e5b58)), closes [#&#8203;7643](https://togithub.com/typescript-eslint/typescript-eslint/issues/7643)
-   **eslint-plugin:** \[prefer-readonly] private fields support ([#&#8203;7686](https://togithub.com/typescript-eslint/typescript-eslint/issues/7686)) ([0e875bf](https://togithub.com/typescript-eslint/typescript-eslint/commit/0e875bf77a9d94dc74924245fabc36c0ae780977))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.8.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#680-2023-10-16)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.7.5...v6.8.0)

##### Bug Fixes

-   **eslint-plugin:** \[consistent-type-imports] import assertion checks added ([#&#8203;7722](https://togithub.com/typescript-eslint/typescript-eslint/issues/7722)) ([afdae37](https://togithub.com/typescript-eslint/typescript-eslint/commit/afdae3739c68469a488277eb7b7f56f679d6eb20))
-   **eslint-plugin:** \[no-shadow] fix static class generics for class expressions ([#&#8203;7724](https://togithub.com/typescript-eslint/typescript-eslint/issues/7724)) ([e5ea1d0](https://togithub.com/typescript-eslint/typescript-eslint/commit/e5ea1d05603e6212093de541e5da49f139571454))
-   **eslint-plugin:** \[no-unsafe-member-access] report on only the accessed property ([#&#8203;7717](https://togithub.com/typescript-eslint/typescript-eslint/issues/7717)) ([f81a2da](https://togithub.com/typescript-eslint/typescript-eslint/commit/f81a2da13529e77d039c5b31b4313a6984ceb964))
-   **eslint-plugin:** \[no-useless-empty-export] exempt .d.ts ([#&#8203;7718](https://togithub.com/typescript-eslint/typescript-eslint/issues/7718)) ([ac397f1](https://togithub.com/typescript-eslint/typescript-eslint/commit/ac397f18176a9defd8c189b5b6b4e5d0b7582210))

##### Features

-   **eslint-plugin:** add new extended rule `prefer-destructuring` ([#&#8203;7117](https://togithub.com/typescript-eslint/typescript-eslint/issues/7117)) ([3c6379b](https://togithub.com/typescript-eslint/typescript-eslint/commit/3c6379b7678bcb190ae70d211cb3930c942d17a0))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### [6.7.5](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.7.4...v6.7.5) (2023-10-09)

##### Bug Fixes

-   **eslint-plugin:** \[prefer-string-starts-ends-with] only report slice/substring with correct range ([#&#8203;7712](https://togithub.com/typescript-eslint/typescript-eslint/issues/7712)) ([db40a0a](https://togithub.com/typescript-eslint/typescript-eslint/commit/db40a0a83abf14237a7a9b3f75d869da26512292))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### [6.7.4](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.7.3...v6.7.4) (2023-10-02)

**Note:** Version bump only for package [@&#8203;typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### [6.7.3](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.7.2...v6.7.3) (2023-09-25)

**Note:** Version bump only for package [@&#8203;typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### [6.7.2](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.7.1...v6.7.2) (2023-09-18)

**Note:** Version bump only for package [@&#8203;typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### [6.7.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.7.0...v6.7.1) (2023-09-18)

**Note:** Version bump only for package [@&#8203;typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.7.5`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#675-2023-10-09)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.7.4...v6.7.5)

##### Bug Fixes

-   **eslint-plugin:** \[prefer-string-starts-ends-with] only report slice/substring with correct range ([#&#8203;7712](https://togithub.com/typescript-eslint/typescript-eslint/issues/7712)) ([db40a0a](https://togithub.com/typescript-eslint/typescript-eslint/commit/db40a0a83abf14237a7a9b3f75d869da26512292))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.7.4`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#674-2023-10-02)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.7.3...v6.7.4)

**Note:** Version bump only for package [@&#8203;typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.7.3`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#673-2023-09-25)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.7.2...v6.7.3)

**Note:** Version bump only for package [@&#8203;typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.7.2`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#672-2023-09-18)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.7.0...v6.7.2)

**Note:** Version bump only for package [@&#8203;typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.7.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#670-2023-09-11)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.6.0...v6.7.0)

##### Bug Fixes

-   **eslint-plugin:** \[no-restricted-imports] disallow side effect imports when allowTypeImports is enabled ([#&#8203;7560](https://togithub.com/typescript-eslint/typescript-eslint/issues/7560)) ([4908905](https://togithub.com/typescript-eslint/typescript-eslint/commit/4908905e4ee2b533504fcba0c671aa869668df25))

##### Features

-   **eslint-plugin:** \[await-thenable] added suggestion fixer ([#&#8203;7437](https://togithub.com/typescript-eslint/typescript-eslint/issues/7437)) ([b284370](https://togithub.com/typescript-eslint/typescript-eslint/commit/b284370e1e95493764d2806cd45975201e02f374))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.6.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#660-2023-09-04)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.5.0...v6.6.0)

##### Bug Fixes

-   **eslint-plugin:** \[key-spacing] consider properties with parens and comments ([#&#8203;7525](https://togithub.com/typescript-eslint/typescript-eslint/issues/7525)) ([7012279](https://togithub.com/typescript-eslint/typescript-eslint/commit/7012279b8510f9fcaee64b610d0a66e8e90f0865))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.5.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#650-2023-08-28)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.4.1...v6.5.0)

##### Bug Fixes

-   **eslint-plugin:** \[consistent-type-assertions] wrap object return value with parentheses ([#&#8203;6885](https://togithub.com/typescript-eslint/typescript-eslint/issues/6885)) ([23ac499](https://togithub.com/typescript-eslint/typescript-eslint/commit/23ac49944e4f4067f89123fddd4a80c629270b4c))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### [6.4.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.4.0...v6.4.1) (2023-08-21)

##### Bug Fixes

-   **eslint-plugin:** \[no-unnecessary-condition] false positives with branded types ([#&#8203;7466](https://togithub.com/typescript-eslint/typescript-eslint/issues/7466)) ([b52658f](https://togithub.com/typescript-eslint/typescript-eslint/commit/b52658fbb6f5cf2085c94926872e6d39efaa3b01)), closes [#&#8203;7293](https://togithub.com/typescript-eslint/typescript-eslint/issues/7293)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.4.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#641-2023-08-21)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.4.0...v6.4.1)

##### Bug Fixes

-   **eslint-plugin:** \[no-unnecessary-condition] false positives with branded types ([#&#8203;7466](https://togithub.com/typescript-eslint/typescript-eslint/issues/7466)) ([b52658f](https://togithub.com/typescript-eslint/typescript-eslint/commit/b52658fbb6f5cf2085c94926872e6d39efaa3b01)), closes [#&#8203;7293](https://togithub.com/typescript-eslint/typescript-eslint/issues/7293)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.4.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#640-2023-08-14)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.3.0...v6.4.0)

##### Bug Fixes

-   **eslint-plugin:** \[non-nullable-type-assertion-style] consider operator precedence when fixing ([#&#8203;7289](https://togithub.com/typescript-eslint/typescript-eslint/issues/7289)) ([bad37a2](https://togithub.com/typescript-eslint/typescript-eslint/commit/bad37a22025b718a10e70cc84b9847eb41f723d0))
-   **eslint-plugin:** \[strict-boolean-expressions] replace dangerous fixer with suggestions ([#&#8203;7394](https://togithub.com/typescript-eslint/typescript-eslint/issues/7394)) ([ad8401a](https://togithub.com/typescript-eslint/typescript-eslint/commit/ad8401a5970441258cc4440a01a3acf35d861171))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.3.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#630-2023-08-07)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.2.1...v6.3.0)

##### Bug Fixes

-   **eslint-plugin:** \[no-extra-parens] keep parens around call expression arguments when type arguments contain parens ([#&#8203;7375](https://togithub.com/typescript-eslint/typescript-eslint/issues/7375)) ([38e5e4e](https://togithub.com/typescript-eslint/typescript-eslint/commit/38e5e4eb8624649a2b66e19a303383bebbda1e2e))
-   **eslint-plugin:** \[no-restricted-imports] allow inline type qualifiers when `allowTypeImports` enabled ([#&#8203;7379](https://togithub.com/typescript-eslint/typescript-eslint/issues/7379)) ([cc9a46d](https://togithub.com/typescript-eslint/typescript-eslint/commit/cc9a46d01bce4282ff841d5ccef5445984aff8f6))

##### Features

-   **eslint-plugin:** \[prefer-nullish-coalescing] allow `ignorePrimitives` option to be `true` ([#&#8203;7331](https://togithub.com/typescript-eslint/typescript-eslint/issues/7331)) ([dfcafae](https://togithub.com/typescript-eslint/typescript-eslint/commit/dfcafae515e7f4d1ae69387eb163200e455dd0ce))

##### Reverts

-   Revert "chore(deps): update dependency marked to v6" ([#&#8203;7429](https://togithub.com/typescript-eslint/typescript-eslint/issues/7429)) ([7891a06](https://togithub.com/typescript-eslint/typescript-eslint/commit/7891a06892445a30c90c882d7e2f17fdf9da5601)), closes [#&#8203;7429](https://togithub.com/typescript-eslint/typescript-eslint/issues/7429) [#&#8203;7422](https://togithub.com/typescript-eslint/typescript-eslint/issues/7422)

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

#### [6.2.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.2.0...v6.2.1) (2023-07-31)

##### Bug Fixes

-   **eslint-plugin:** \[no-inferrable-types] apply also for parameter properties ([#&#8203;7288](https://togithub.com/typescript-eslint/typescript-eslint/issues/7288)) ([67f93b1](https://togithub.com/typescript-eslint/typescript-eslint/commit/67f93b19f2e481a4e441635d72e81de9d5d7ad44))
-   **scope-manager:** correct decorators(.length) check in ClassVisitor for methods ([#&#8203;7334](https://togithub.com/typescript-eslint/typescript-eslint/issues/7334)) ([abbb6c2](https://togithub.com/typescript-eslint/typescript-eslint/commit/abbb6c2c6d2bc1f8d4defd2060dbc473735b2cc7))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

### [`v6.2.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#621-2023-07-31)

[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.2.0...v6.2.1)

##### Bug Fixes

-   **eslint-plugin:** \[no-inferrable-types] apply also for parameter properties ([#&#8203;7288](https://togithub.com/typescript-eslint/typescript-eslint/issues/7288)) ([67f93b1](https://togithub.com/typescript-eslint/typescript-eslint/commit/67f93b19f2e481a4e441635d72e81de9d5d7ad44))
-   **scope-manager:** correct decorators(.length) check in ClassVisitor for methods ([#&#8203;7334](https://togithub.com/typescript-eslint/typescript-eslint/issues/7334)) ([abbb6c2](https://togithub.com/typescript-eslint/typescript-eslint/commit/abbb6c2c6d2bc1f8d4defd2060dbc473735b2cc7))

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/relea

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/patternfly/patternfly-react).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy45My4xIiwidXBkYXRlZEluVmVyIjoiMzcuMTczLjAiLCJ0YXJnZXRCcmFuY2giOiJtYWluIn0=-->

user: renovate[bot]
issue_9897: state: open
title: Followup to #9853 Masthead
body: update react masthead examples to match core


user: mattnolting
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_9896: state: open
title: Bug - Table Demo - Column management drag and drop using removed props
body: See example here: https://www.patternfly.org/components/table/react-demos/#column-management-with-draggable

The example is old and attempting to use deprecated/removed `onDrag` props rather than the new `DragDrop`/`Droppable` components. It also appears to be using the deprecated table even though it is not in the deprecated tab.

This example of a draggable data-list could come in helpful for this story: https://www.patternfly.org/components/data-list#draggable
user: gitdallas
issue_9893: state: open
title: react-charts: ChartLabel not compatible with TypeScript 5.x
body: **Describe the enhancement or change**
I use `@patternfly/react-charts:7.1.2` with RedHat console.dot starter project https://github.com/RedHatInsights/frontend-starter-app

`frontend-starter-app` has moved to TypeScript [5.x](https://github.com/RedHatInsights/frontend-starter-app/pull/593/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R57) from 4.x.

This however brings problems when using `@patternfly/react-charts:7.1.2` which still uses TypeScript 4.x.

This [line](https://github.com/patternfly/patternfly-react/blob/main/packages/react-charts/src/components/ChartLabel/ChartLabel.tsx#L233) fails to compile with TS 5.x:
```
ERROR in ./node_modules/@patternfly/react-charts/src/components/ChartLabel/ChartLabel.tsx:233:92
TS2345: Argument of type 'CSSProperties | undefined' is not assignable to parameter of type 'CSSProperties'.
  Type 'undefined' is not assignable to type 'Properties<string | number, string & {}>'.
    231 |       }
    232 |     );
  > 233 |   const newStyle = Array.isArray(style) ? style.map(applyDefaultStyle) : applyDefaultStyle(style);
        |                                                                                            ^^^^^
    234 |
    235 |   return <VictoryLabel style={newStyle as any} textAnchor={textAnchor} {...rest} />;
    236 | };

Found 1 error in 2818 ms.
```
It is OK with TypeScript 4.x

**Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?**
Yes, I work for Red Hat on the Ansible Project.

I am writing a new console.dot extension and am tied to the latest `frontend-starter-app` that uses TypeScript 5.x (and PatternFly 5.x - I see you are using PF5 pre-release.. IDK if you need a general dependency upgrade?)

**Any other information?**

user: manstis
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_9884: state: open
title: Bug - Card - Card header actions take up more than 50% width 
body: **Describe the problem**
When the window width is reduced, the card header actions take up more than 50% of the horizontal width.

Before (PF4):
<img width="620" alt="Screenshot 2023-12-12 at 3 59 56 PM" src="https://github.com/patternfly/patternfly-react/assets/869106/4c6a14cb-de5e-41a5-a783-466b06c42a96">

After (PF5):
<img width="619" alt="Screenshot 2023-12-12 at 4 00 08 PM" src="https://github.com/patternfly/patternfly-react/assets/869106/5270e9e9-68fb-4759-a896-501a2f5ea820">


**How do you reproduce the problem?**
https://codesandbox.io/p/sandbox/card-header-space-issue-p2g5sn?file=%2Findex.tsx%3A7%2C8
Slide the preview window smaller

**Expected behavior**
Would expect to see the actions take up no more than 50% of the horizontal width

**What is your product and what release date are you targeting?**
OCM, Q4 2022

**Workaround**
```
.pf-v5-c-card__header-main {
    flex-basis: auto;
  }
```
user: jschuler
issue_9883: state: open
title: DragDropSort - spike - keyboard scrolling behavior
body: Look into dndkit and see if we can prevent the keyboard sensors from automatically scrolling the page on every arrow up/down (ideally it should only be scrolling when it reaches the page boundary instead).
user: kmcfaul
issue_9875: state: open
title: Bug - Card - Cannot deselect a clickable card
body: **Describe the problem**
I'd like to be able to deselect an active card. Essentially similar to this deprecated example: https://www.patternfly.org/components/card/#selectable-card-accessibility-features-deprecated

**How do you reproduce the problem?**
[Provide steps to reproduce. A [codesandbox](https://codesandbox.io/s/serverless-cherry-q9t3f ) demonstrating the problem is appreciated.](https://codesandbox.io/p/sandbox/staging-thunder-xd5qhs?file=%2FCard.tsx)

user: jschuler
issue_9874: state: open
title: CodeEditor - verify & update readme steps
body: Block about peer dependencies shouldn't be necessary.
Block about create-react-app should be verified and may no longer be needed.
user: kmcfaul
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9872: state: open
title: Bug - Docs - Card docs mentions isSelectableRaised is preferred
body: Docs mention that `isSelectableRaised` is preferred over `isSelectable`, but in reality `isSelectableRaised` is deprecated?

https://www.patternfly.org/components/card#selectable-cards-deprecated
user: jschuler
issue_9869: state: open
title: Bug - [Tabs] - [Vertical Tabs show content below tablist instead of beside]
body: **Describe the problem**
When using vertical tabs, the content is rendered below the tablist.
This looks a bit strange, especially when using boxed tabs.

**How do you reproduce the problem?**
This behavior is shown on the Patternfly website: https://www.patternfly.org/components/tabs#vertical-tabs:
![288537127-536b0c86-003d-47a4-9b49-18848fece0a4](https://github.com/patternfly/patternfly-react/assets/2582866/0ae46fde-9b91-4b5a-9e77-89d3570db0d9)

Note that the tablist fills the entire width of the demo.

So you can use [the code from that example](https://codesandbox.io/p/sandbox/old-sky-js8c49)

Expected behavior
The content is displayed to the right of the tablist, as the design (especially if the tabs are boxed) indicates.

I could sort of replicate what I want by wrapping both the tablist and the content in a flexbox.

```
<div class="pf-v5-c-tabs pf-m-vertical pf-m-box">
  <div style="display: flex;">
    <ul class="pf-v5-c-tabs__list">...</ul>
    <section class="pf-v5-c-tab-content">Users</section>
  </div>
</div>
```

yields:

![288542503-b60707b4-729b-41ef-824f-a785343c2e3a](https://github.com/patternfly/patternfly-react/assets/2582866/970244cf-afd3-4353-8a51-f699164a9f14)

**Is this issue blocking you?**
The current workaround is to use detached tabs and place the tabs and the content in a grid and manually specifying how large each side should be.

**Screenshots**
If applicable, add screenshots to help explain the issue.

**What is your environment?**
 - OS: [e.g. iOS]
 - Browser [e.g. chrome, safari]
 - Version [e.g. 22]

**What is your product and what release date are you targeting?**

OS: Arch Linux
Browser: Firefox

> This is a copy of the original issue https://github.com/patternfly/patternfly/issues/6117 and I moved here since I believe it fits more the ReactJS library rather than the Patternfly repo itself.

user: carlosthe19916
issue_9868: state: open
title: Page - add example showing different type prop variants
body: **Describe the enhancement or change**
We should add an example similar to Core's [main section variants example](https://www.patternfly.org/components/page/html#main-section-variations). Followup to comment https://github.com/patternfly/patternfly-react/pull/9848#pullrequestreview-1767759654

**Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?**

**Any other information?**

user: thatblindgeye
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9847: state: open
title: Bug - Select - cannot change MenuContent properties
body: **Describe the problem**
It's currently not possible to pass props from `<Select>` down to a `<MenuContent>` (e.g. `maxMenuHeight`)
[This line](https://github.com/patternfly/patternfly-react/blob/main/packages/react-core/src/components/Select/Select.tsx#L161) seems to be culprit

**How do you reproduce the problem?**
[codesandbox here](https://codesandbox.io/p/sandbox/vibrant-bas-kjrzvq)

**Expected behavior**
Expected to be able to adjust the menu content via props

**Is this issue blocking you?**
Not blocking, a `<SelectList>` can be wrapped in a `<Panel>` which can be adjusted.
user: michpetrov
issue_9834: state: open
title: Bug - Table -> React demos -> Sortable-responsive - incorrect pagination in readme demo
body: **Describe the problem**
In the readme under Tables -> React demos -> [Sortable - responsive ](https://www.patternfly.org/components/table/react-demos/#sortable---responsive) in the React.useEffect 
```setSortedRows(sortedData.slice((page - 1) * perPage, page * perPage - 1));``` should be ```setSortedRows(sortedData.slice((page - 1) * perPage, page * perPage));``` because slice end is exclusive. The demo code says the pagination is pages 1-10 but only shows nine results. 

**Expected behavior**
The example code should be changed to
```typescript
React.useEffect(() => { 
    setSortedRows(sortedData.slice((page - 1) * perPage, page * perPage));
}, [sortedData, page, perPage]);
``` 


**What is your environment?**
 - Readme: Release 5.1.0


user: keckrich
issue_9827: state: open
title: Bug - ToolbarToggleGroup - a11y error gets flagged due to aria-controls having invalid value
body: **Describe the problem**
Before an update made in https://github.com/patternfly/patternfly-react/pull/9621 which conditionally renders the `aria-controls` attribute, some demos were getting a11y errors raised due to the fact that the value passed into the `aria-controls` prop was an invalid `id` (whatever element was meant to have that `id` wasn't rendered in the DOM, and aria-controls needs to be passed a valid `id`).

Per discussion with @jenny-s51 conditionally rendering aria-controls offers a (possibly temporary) fix to the a11y issue, but we should investigate whether or not that is a suitable fix long term. Ideally it may be better to have aria-controls always pointing to a valid element rather than conditionally applying the attribute.


**How do you reproduce the problem?**
Provide steps to reproduce. A [codesandbox](https://codesandbox.io/s/serverless-cherry-q9t3f ) demonstrating the problem is appreciated.

**Expected behavior**
A clear and concise description of the expected behavior.

**Is this issue blocking you?**
List the workaround if there is one.

**Screenshots**
If applicable, add screenshots to help explain the issue.

**What is your environment?**
 - OS: [e.g. iOS]
 - Browser [e.g. chrome, safari]
 - Version [e.g. 22]

**What is your product and what release date are you targeting?**

**Any other information?**

user: thatblindgeye
issue_9825: state: open
title: Update several TreeView unit tests
body: **Describe the enhancement or change**
Followup to #9773, some tests could use some updating

- Update tests that are using `getByText(...).tagName.toBe("BUTTON")` so that they use getByRole("button") instead
- In TreeViewRoot, add tests for hasCheckboxes and hasSelectableNodes; should first try testing if pressing Tab focuses the correct element, otherwise try using a `user.click` event, *otherwise* just check that the tabindex attribute is applied to the correct element
- In TreeViewList, update the "Renders toolbar content when toolbar prop is passed" test to check that `getByrole('separator')` is in the doc, and update "Does not render toolbar content when toolbar prop is not passed" test to check that `queryByText...` is not in the doc
- check that any `getByRole('button')` calls are also passing in the `{name: ...}` options object

**Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?**

**Any other information?**

user: thatblindgeye
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_9824: state: open
title: Ability to add ID to input in SearchInput component
body: Konveyor QE are picky about having IDs on input fields. The current SeachInput component (and the TextInputGroupMain component it wraps) does not allow for an ID on that element.

Can we add a `inputID` prop that could get passed through to the input element?
user: gitdallas
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9823: state: open
title: cleanup - DataListAction - id, aria-label and aria-labelledby are not currently in use but are required
body: `id` can probably remain (and if so should be made non-required) but `aria-label` and `aria-labelledby` should be removed because they don't usually exist on a div without a role. These props were a holdover from when we were using a `Button` internally opposed to `children`. 
user: kmcfaul
issue_9821: state: open
title: CodeEditor - support Mac and PC shortcuts in example
body: **Describe the enhancement or change**
Followup to updates made to a11y docs and conversation at https://github.com/patternfly/patternfly-org/pull/3799#discussion_r1383460463

The [with shortcut menu and main header content example](https://www.patternfly.org/components/code-editor#with-shortcut-menu-and-main-header-content) is setup to only render a list of keys as `A + B + C + n...`. It'd be beneficial to have the example show the shortcuts menu supporting both Mac and PC shortcuts.

**Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?**

**Any other information?**

user: thatblindgeye
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9820: state: open
title: Migration guides for deprecated components
body: A skeleton of the guides we want to write has been created in [this doc](https://docs.google.com/document/d/11_6Xe-E1HbGYCoOK0clq-dEN-hujPUtD-EF6vH4-c80/edit#heading=h.ii0as9329z73).


```[tasklist]
### Tasks
- [x] Table - sortable
- [x] Table - selectable
- [x] Table - expandable
- [x] Table - compound expandable
- [x] Table - with actions
- [x] Table - empty state
- [x] Table - favoriable
- [x] Table - tree
- [ ] Table modifiers
- [x] Select - single
- [x] Select - checkbox
- [x] Select - typeahead
- [ ] Select - with inline filtering
- [ ] Select - modifiers
- [ ] Select - composable favorites
- [ ] Select - composable custom panel
- [ ] Dropdown - basic
- [ ] Dropdown - tooltips on disabled items
- [ ] Dropdown - with autofocus
- [ ] Dropdown - toggle styles
- [ ] Dropdown - menu behaviors
- [ ] Dropdown modifiers
- [ ] Wizard (guides TBD)
- [ ] Application launcher (guides TBD)
- [ ] Context selector (guides TBD)
- [ ] Options menu (guides TBD)
- [ ] Page header (guides TBD)
```

We will also want to incorporate any information from @mturley's table batteries effort 

user: nicolethoen
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9816: state: open
title: Spike - Investigate options for updating a11y props being required or not
body: **Describe the enhancement or change**
Spike for a discussion to have regarding https://github.com/patternfly/patternfly-react/issues/5397

Basically we need to decide whether:

- we want to update certain a11y props to either be required (if currently optional) or make them optional (if currently required)
- we want to add console warnings when an optional a11y prop is not passed in, but ideally should be (e.g. if an element doesn't have a visible text label, typically we should want an `aria-label` added somewhere)
- leave things as-is - props will remain optional or required as they already are
- some combination of all of the above

**Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?**

**Any other information?**

user: thatblindgeye
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_9802: state: open
title: JumpLinks - add aria-labelledby prop and warning for aria labels
body: **Is this a new component or an extension of an existing one?**
JumpLinks

**Describe the feature**
Follow up to comments in https://github.com/patternfly/patternfly-org/pull/3808

Basically right now the default value of the `aria-label` on JumpLinks is set to the `label` prop if passed in, and only if `label` is a string. Ideally we should consider making updates so that:

- an `aria-labelledby` prop can be passed in which can be given an `id` of the `label` element or some other element that labels the jump links nav. 
- if `label` is not a string and `aria-labelledby` is not manually passed in, generate a random `id` internally that's applied to the `label` wrapper element (pf-v5-c-jump-links__label), with that `id` passed to an aria-labelledby attribute on the outer JumpLinks `nav` element. 
- We could also consider removing the default value of the `aria-label` prop, but that may need to wait for a breaking change. Rationale here is that it would make more sense to link to the visible text label via `aria-labelledby` rather than repeat the text in an `aria-label`; while React is automating that for the consumer, it's only when the label prop is a string and in the HTML implementation there isn't that same automation provided by us

We should also add in a console warning if neither `aria-label` or `aria-labelledby` are passed in, otherwise there's a chance that the JumpLinks internal `nav` has no proper accessible name.

**Are there visuals for this feature? If applicable, please include examples for each state and for varying widths**
Include screenshots or links to Marvel or other mockups.

**Any other information?**
A followup will need to be made in org to add verbiage to the a11y docs for JumpLinks
user: thatblindgeye
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9799: state: open
title: Convert right-to-left demo to TS
body: https://github.com/patternfly/patternfly-react/blob/main/packages/react-core/src/demos/RTL/examples/PaginatedTable.jsx

https://react-staging.patternfly.org/patterns/right-to-left/react-demos/paginated-table/

FWIW the RTL demo is a modified version of the [table column management demo](https://github.com/patternfly/patternfly-react/blob/main/packages/react-table/src/docs/demos/table-demos/ColumnManagement.jsx) 
user: mcoker
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_9796: state: open
title: CodeEditor - add example showcasing custom keyboard shortcuts
body: **Is this a new component or an extension of an existing one?**
CodeEditor

**Describe the feature**
Followup to an update made to the a11y docs in org: https://github.com/patternfly/patternfly-org/pull/3799#discussion_r1383463429

Content showing how to add custom keyboard shortcuts are removed in that PR, but we don't really document elsewhere how to do so.


user: thatblindgeye
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_9793: state: open
title: Bug - address vulnerabilities
body: ## react-charts
### high severity
Introduced through: lodash@4.17.20, victory-area@36.6.11 and others
Fixed in: lodash@4.17.21

## react-table
### high severity
Introduced through: lodash@4.17.20
Fixed in: lodash@4.17.21

## eslint-plugin-patternfly-react
### high severity
Introduced through: eslint-plugin-jsx-a11y@6.7.1, eslint-plugin-node@11.1.0 and others
Fixed in: semver@5.7.2, @6.3.1, @7.5.2

reported by: [snyk app](https://app.snyk.io/org/patternfly/projects?groupBy=targets&searchQuery=&sortBy=highest+severity&filters[Show]=&filters[Integrations]=&before&after)
user: nicolethoen
issue_9788: state: open
title: Bug [v5.1.0] - Select Component - User is not able to navigate using the keyboard arrow keys when component is selected using the mouse
body: **Describe the problem**

The user is not able to navigate using the keyboard arrow keys when component is selected using a mouse click but it works when component is selected using the tab or enter key.

This behaviour is seen in the select variants which are not typeahead like single select, select with checkbox, etc.

**How do you reproduce the problem?**

I'm using Chrome browser (but reproducible in Safari and Firefox).

1. Select the select component (single or checkbox variant) using mouse.
2. Try to navigate using keyboard arrow keys.

Sandbox links-

[Single select](https://codesandbox.io/s/gg5lxg)
[Select with Checkbox](https://codesandbox.io/s/dqnkhv)

**Expected behavior**

Select component (single variant, select with checkbox) should allow keyboard navigation regardless (mouse or keyboard) the way user selects it.

**Is this issue blocking you?**

This is a critical issue as the select components are used at various places in our customer-facing application.


user: aakankshabhende
issue_9783: state: open
title: Bug - Pagination - bottom pagination layout broken in mobile
body: Reported by ansible:

<img width="482" alt="278058534-2e102cef-a06a-4a0e-ad12-e2cfcf5e1d6b" src="https://github.com/patternfly/patternfly-react/assets/26305082/91a65609-a095-4c25-b531-9a4e9c7923cd">


according to @mcoker: "In react, looks like there is a `<div>` that wraps the menu toggle that should ideally be removed or set to `display: contents`. The toggle's positioning relies on being a direct child of the `.pf-v5-c-pagination` element parent since the layout is controlled via flex."
user: nicolethoen
issue_9778: state: open
title: Bug - ClipboardCopy - ClipboardCopyToggle has a div within a button
body: Followup to https://github.com/patternfly/patternfly/issues/6019

**Describe the problem**
ClipboardCopy's expansion toggle currently has a div within a button, which is invalid markup.

**Expected behavior**
The `pf-v5-c-clipboard-copy__toggle-icon` element should be a span rather than a div.
user: wise-king-sullyman
issue_9777: state: open
title: Menu - update drilldown inline filter example markup
body: **Describe the enhancement or change**
Currently the [Menu with drilldown and inline filter](https://www.patternfly.org/components/menus/menu/#with-drilldown-and-inline-filter) example is rendering the search filter (drilled into level 2) as a div inside a `ul` element, causing an axe error to be flagged (since only `li` element should be direct children). Either the search input should be moved outside of the menu list or should be rendered within an `li` as well.

**Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?**

**Any other information?**

user: thatblindgeye
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9767: state: open
title: Consider adding Type documentation
body: **Describe the enhancement or change**
Branching off from a conversation at https://github.com/patternfly/patternfly-react/pull/9709#pullrequestreview-1690213766, our Wizard component has several types that aren't really documented, but are still mentioned in the Prop tables. For example the Wizard's `nav` prop has a type of WizardNavType, which itself includes the CustomWizardNavFunction type, neither of which are explained on the Wizard component page (though there is an example that uses the CustomWizardNavFunction)



user: thatblindgeye
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9755: state: open
title: Nav - add wrapper to Nav link item text by default
body: **Describe the enhancement or change**
A clear and concise description of the request. What is the expected outcome?

Update `NavItem` to add the Nav link text wrapper (`.pf-v5-c-nav__link-text`) by default instead of as an opt-in.    Remove the `hasNavLinkWrapper` opt-in prop.
user: tlabaj
labels: breaking change :boom:: this change requires a major release and has API changes.
DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9713: state: open
title: feat(ClipboardCopy): 9712 allow alternative title
body: Closes #9712 

https://patternfly-react-pr-9713.surge.sh/components/clipboard-copy#expanded-with-alternate-title

unsure if my verbiage/naming was the best.

setting a title will force the title itself to be readOnly (disabled textinput), but a user can still edit the text that gets copied if there is expandable content for them to do it in the text area, unless `isReadOnly` is specified in which case they wouldn't be able to edit either place.
user: gitdallas
issue_9712: state: open
title: Clipboard Copy - add support for a title on the expandable ClipboardCopy
body: **Is this a new component or an extension of an existing one?**
New feature for ClipboardCopy

**Describe the feature**
It's been requested that we add an option to specify a title on expandable ClipboardCopy which is decoupled from the text which is shown in the expanded section and is copied.

**Are there visuals for this feature? If applicable, please include examples for each state and for varying widths**
![image](https://github.com/patternfly/patternfly-react/assets/7115053/664cd998-4cd9-440d-8454-13a56a25fbe0)


**Any other information?**

user: wise-king-sullyman
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_9695: state: open
title: Checkbox/Radio - add support for aria-describedby
body: follow up to https://github.com/patternfly/patternfly/issues/5803 for checkbox/radio with `description` prop set
user: mcoker
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_9689: state: open
title: Expandable section - update unit tests
user: mfrances17
issue_9688: state: open
title: Empty state - update unit tests
user: mfrances17
issue_9686: state: open
title: Drag and drop - update unit tests
user: mfrances17
issue_9685: state: open
title: Date picker - update unit tests
user: mfrances17
issue_9679: state: open
title: Consume core updates: Table
body: Follow up to core [table](https://github.com/patternfly/patternfly/issues/5728) updates 

user: andrew-ronaldson
issue_9678: state: open
title: Consume core updates: Form, Text input group, input group, form control, checkbox, radio, number input
body: Follow up to Core work on [Forms](https://github.com/patternfly/patternfly/issues/5706)

Core PR https://github.com/patternfly/patternfly/pull/6135
```[tasklist]
### Tasks
- [ ] https://github.com/patternfly/patternfly-react/issues/9931
- [ ] https://github.com/patternfly/patternfly-react/issues/9978
```

user: andrew-ronaldson
issue_9656: state: open
title: Charts - investigate lang direction detection
body: Investigate possibility to automatically set direction for `legendDirection` and `invertAxis` props that support chart RTL.
user: kmcfaul
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_9653: state: open
title: Menu/MenuItem - should support drill-[up/out] icon/layout in menu list
body: re: https://github.com/patternfly/patternfly-react/issues/9587 and this issue to make the same update in core https://github.com/patternfly/patternfly/issues/5950. Not sure if this is a breaking change or not, probably depends on how we go about implementing it.

In the drilldown with breadcrumb menu examples, in the breadcrumb dropdown, we have items that present (and seem to function) as drill-[up/out] items with a back arrow at the start of the item, and clicking on the item takes you up a level in the breadcrumb hierarchy. However, our component doesn't support this layout - our examples are using a user-supplied icon passed as the `icon` prop - https://github.com/patternfly/patternfly-react/blob/e27aac2f35e0a8bb16fa5397eb5ef841b3ecc578/packages/react-core/src/components/Menu/examples/MenuWithDrilldownBreadcrumbs.tsx#L130-L138

Some issues with this are:
1. It doesn't work by default in RTL since we can't predictably target and mirror/flip that menu item icon for the user since that could be a non-directional icon or they may have opted for some other type of directional icon there that shouldn't be flipped.
2. Since it's a user supplied icon, there is the possibility for inconsistency
3. I could be wrong, but I don't know if a user could pass an actual icon to any of those items since the prop is being used for the back arrow.

We have a `direction="up"` prop that puts the correct icon container and icon on a drill-up/out icon and works in RTL, but that is specific to the top/first item in a drilled-in drilldown menu. The prop applies other logic to that item that isn't appropriate for use in the breadcrumb items, so we can't use that prop there. https://github.com/patternfly/patternfly-react/blob/e27aac2f35e0a8bb16fa5397eb5ef841b3ecc578/packages/react-core/src/components/Menu/MenuItem.tsx#L366-L370

Ideally we could do something like update the `direction` prop so it could be used in these breadcrumb menu items or maybe introduce some new kind of prop for an item that indicates clicking it does some kind of "back" action and it just borrows the way `direction="up"` includes the icon in the item.
user: mcoker
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_9644: state: open
title: Tabs & Nav - scroll button aria labels
body: The properties for the scroll buttons in Nav (`ariaLeftScroll` and `ariaRightScroll`) and Tabs (`leftScrollAriaLabel` and `rightScrollAriaLabel`) should use `back` and `forward` instead of `left` and `right` to better reflect what each button is doing between LTR/RTL languages.
user: kmcfaul
labels: breaking change :boom:: this change requires a major release and has API changes.
Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_9641: state: open
title: ToolbarItem - expand-all variant should include expand all icon
body: re: https://github.com/patternfly/patternfly-react/pull/9605/files

The expand all icon is currently something the user passes, but for us to mirror it automatically in RTL in the CSS, our component should be updated to include it for the user. This button is primarily for an expandable data-list and table, and the expand toggles in those components supply the icon, so the toolbar probably should, too, and would provide consistency in the icons used. We could probably do it a couple of ways:

1. Keep everything the way it is now, but update `<ToolbarExpandIconWrapper>` to include the icon for the user. And rename it to `<ToolbarExpandAllIcon>`? That aligns with the core class. IMO that should be updated whether we use it as a wrapper or not.
1. Update `<ToolbarItem variant="expand-all">` to bundle the 1) toggle button, 2) `<ToolbarExpandIconWrapper>`/`<ToolbarExpandAllIcon>`, and 3) the icon. Chatting with @thatblindgeye, we could also allow tooltip props in case someone wants a tooltip for the button.

As far as I can tell, the data list and table do not allow the user to pass their own icon to the expandable toggle, so I don't know that we need to allow for that in the toolbar, either? If we do, there is a question of whether it should go in `<ToolbarExpandIconWrapper>`/`<ToolbarExpandAllIcon>` or not, which will rotate (when expanded) and mirror (in RTL) the icon the user passes.

My vote would be for the second option.
user: mcoker
labels: breaking change :boom:: this change requires a major release and has API changes.
Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_9580: state: open
title: [PageSection] - change padding for adjacent page sections with the same background color
body: **Is this a new component or an extension of an existing one?**
`PageSection` is an existing component.

**Describe the feature**
`PageSection` has multiple variants with different colored backgrounds. The padding all around each section is currently `24px`. When adjacent sections have different color backgrounds, the spacing works well. But when adjacent sections have the same background, it looks like a lot of blank space. This has come up in discussions with our UX where the request was to reduce the spacing between adjacent sections.

While it is easy enough to remove the top padding with an override, us devs want to adhere to the PF prescribed layouts. Therefore this is a request to formally adopt such a layout change in the `PageSection` component.

**Are there visuals for this feature? If applicable, please include examples for each state and for varying widths**
![image](https://github.com/patternfly/patternfly/assets/14068621/ee6ec8c2-b733-4ecf-972a-c4c557b19614)

![image](https://github.com/patternfly/patternfly/assets/14068621/81628ca3-b07b-4380-8253-1004a16b0eb8)
vs
![image](https://github.com/patternfly/patternfly/assets/14068621/81c95130-6b6c-4b42-a4d8-1e7c3a4b5440)

**Any other information?**

user: christianvogt
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_9576: state: open
title: Popper - investigate whether logical properties can be used
body: **Is this a new component or an extension of an existing one?**
Popper

**Describe the feature**
Related to https://github.com/patternfly/patternfly/issues/5886

Before going further with the above issue, we should look into whether Popper can support using logical properties instead of directional, e.g. "block-start" instead of "top", in some fashion.


**Are there visuals for this feature? If applicable, please include examples for each state and for varying widths**
Include screenshots or links to Marvel or other mockups.

**Any other information?**

user: thatblindgeye
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_9534: state: open
title: Code editor
user: tlabaj
issue_9528: state: open
title: Calendar month test updates
user: wise-king-sullyman
issue_9517: state: open
title: Bug - MenuItem- Tooltips on MenuItems aren't being announced
body: **Describe the problem**
MenuItem

**How do you reproduce the problem?**
Navigate to a menu item with tooltip in our [Menu examples](https://www.patternfly.org/components/menus/menu) (first example has a tooltip on the first aria-disabled item) with VoiceOver/a screen reader, notice that the tooltip doesn't get announced.

**Expected behavior**
The tooltip content gets announced when it is rendered

**Any other information?**
Seems the `aria-describedby` attribute isn't being applied to the internal button of MenuItem when the Tooltip renders
user: thatblindgeye
issue_9515: state: open
title: File Upload - Implement combined File upload
body: **Is this a new component or an extension of an existing one?**
New component which combines the single and multiple file upload functionality

This is a placeholder until [the design](https://github.com/patternfly/patternfly-design/issues/1223) is complete and any needed work is done in core.

When implementing we should consider the API concerns expressed here: https://github.com/patternfly/patternfly-react/issues/3966

user: wise-king-sullyman
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_9511: state: open
title: [Select] The new typeahead select implementation is not hiding boilerplate code at all
body: **Describe the enhancement or change**
The new typeahead requires for the user to implement all the keyboard navigation and generally all event handling manually.

```
  const handleMenuArrowKeys = (key: string) => {
    let indexToFocus;

    if (isOpen) {
      if (key === 'ArrowUp') {
        // When no index is set or at the first index, focus to the last, otherwise decrement focus index
        if (focusedItemIndex === null || focusedItemIndex === 0) {
          indexToFocus = selectOptions.length - 1;
        } else {
          indexToFocus = focusedItemIndex - 1;
        }
      }

      if (key === 'ArrowDown') {
        // When no index is set or at the last index, focus to the first, otherwise increment focus index
        if (focusedItemIndex === null || focusedItemIndex === selectOptions.length - 1) {
          indexToFocus = 0;
        } else {
          indexToFocus = focusedItemIndex + 1;
        }
      }

      setFocusedItemIndex(indexToFocus);
      const focusedItem = selectOptions.filter((option) => !option.isDisabled)[indexToFocus];
      setActiveItem(`select-multi-typeahead-${focusedItem.value.replace(' ', '-')}`);
    }
  };

  const onInputKeyDown = (event: React.KeyboardEvent<HTMLInputElement>) => {
    const enabledMenuItems = selectOptions.filter((menuItem) => !menuItem.isDisabled);
    const [firstMenuItem] = enabledMenuItems;
    const focusedItem = focusedItemIndex ? enabledMenuItems[focusedItemIndex] : firstMenuItem;

    switch (event.key) {
      // Select the first available option
      case 'Enter':
        if (!isOpen) {
          setIsOpen((prevIsOpen) => !prevIsOpen);
        } else if (isOpen && focusedItem.value !== 'no results') {
          onSelect(focusedItem.value as string);
        }
        break;
      case 'Tab':
      case 'Escape':
        setIsOpen(false);
        setActiveItem(null);
        break;
      case 'ArrowUp':
      case 'ArrowDown':
        event.preventDefault();
        handleMenuArrowKeys(event.key);
        break;
    }
  };
```

This is the example code for the keyboard navigation. This code should not be exposed to the developers as it's unlikely that it needs to be changed. Settings the focused and active items should be implemented internally and hidden. 

**Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?**

This is just an ehnancement request and definitely not a blocker. However, for this specific component the developer experience has heavily degraded with the upgrade to Patternfly 5.
user: KKoukiou
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9482: state: open
title: Next Toolbar: refactor to be composable 
body: **Describe the enhancement or change**
A clear and concise description of the request. What is the expected outcome?
Refactor the Toolbar API so the component is composable.  Introduce new implementation as a Next component. 

user: tlabaj
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9460: state: open
title: Update contribution guide to include guidelines for deprecated components
body: **Describe the enhancement or change**
What it means for a component to be deprecated is currently unclear to our consumers.

Our contribution guidelines should explain what a component being deprecated entails, including how long it will still be available and how it impacts what work will be done on it going forward.

user: wise-king-sullyman
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9443: state: open
title: Update all instance of old PF logo in examples and demos to new logo
body: **Describe the enhancement or change**
Update all instance of old PF logo in examples and demos to new logo

component examples:
- About Modal
- Background image
- Brand
- Card
- Login Page

Demos:

-  Card
- Custom menus/ composable menu demos
- ~~notification drawer~~
- ~~wizard demo~~



user: tlabaj
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9441: state: open
title: Some tooltip tests unexpectedly failing
body: **Describe the enhancement or change**
Related to https://github.com/patternfly/patternfly-react/pull/9283 (where tests were temporarily skipped), possibly related to https://github.com/patternfly/patternfly-react/pull/9339

Some tests failed in 9283 linked above despite not touching the Tooltip component. May be related to updates made to 9339. Either way we'll need to look into updating or removing tests if they are no longer applicable to Tooltip.

**Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?**

**Any other information?**

user: thatblindgeye
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_9413: state: open
title: Component updates to support Penta
body: This is an Epic issue that will tracks any follow up work need once core has made their Penta component updates.  
This is a task list that correlates with the core issues for Penta component updates.  There may be cases where the react component does not need any work.  If that is the case we can disregard the task item. 

_This timeline offers extra time for any issues that arise in implementation and testing._


- [ ] Implement any necessary adjustments to the mechanism for including CSS in React. 
- [ ] #9678
- [x] #9844
- [x] #9676
- [x] #9908
- [x] #9674
- [x] #9677
- [ ] #9923
- [x] #9680
- [x] #9843
- [x] #9675
- [ ] #9984
- [x] #9924
- [ ] #10010
- [x] #9879
- [x] #9990
- [x] #9993
- [x] #9995
- [ ] #9679
- [x] #9849
- [x] #9681
- [ ] #9927
- [x] #9860
- [x] #9928
- [x] #9998
- [x] #9999
- [x] #10003
- [x] #9917
- [x] #9911
- [x] #10004
- [x] #10007
- [ ] #10008
- [ ] #10009
- [x] #9855


user: tlabaj
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_9407: state: open
title: Select - When Inline filter field is open, allow us to also specify a valid pattern that can be searched
body: **Is this a new component or an extension of an existing one?**
Select

**Describe the feature**
When an inline filter is open user can type any characters. even though we might know the selections are only using digits, etc.
If this happens, the component just says:
    noResultsFoundText: 'No results found',
Ideally it would say the entered text contains letters when it should just contain numbers, etc

**Are there visuals for this feature? If applicable, please include examples for each state and for varying widths**
maybe this?
<img width="345" alt="CleanShot 2023-07-26 at 11 13 15@2x" src="https://github.com/patternfly/patternfly-react/assets/60980397/8720ac38-0e03-4451-874b-020c6e73fa46">


**Any other information?**

user: jeswanke
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_9340: state: open
title: Bug - [Tree view] - [Update search to use the SearchInput component]
body: **Describe the problem**
A clear and concise description of the problem. Which components are affected?
Update search to use the SearchInput component

https://github.com/patternfly/patternfly-react/blob/f038112114d5416ef598135f46ee04ecf33f8d92/packages/react-core/src/components/Menu/examples/MenuFilteringWithSearchInput.tsx#L48-L52



user: tlabaj
labels: breaking change :boom:: this change requires a major release and has API changes.
issue_9332: state: open
title: Remove redundant string type
body: **Describe the enhancement or change**
Several spots we're typing a prop as both "string" and "React.ReactNode", we should remove "string" since ReactNode will include the string type.

- NotificationDrawerGroup
- OptionsMenuItemGroup
- Select (deprecated)
- TableTypes
- Table MD file

All of the above are using `string | React.ReactNode`. Follow up from comment https://github.com/patternfly/patternfly-react/pull/9278#discussion_r1253128007

**Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?**

**Any other information?**

user: thatblindgeye
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_9326: state: open
title: Bug - Dropdown - When dropdown opens and outer page gets overflow, scrolling down is stuck
body: **Describe the problem**
Using the Dropdown component in a table row, causes sometimes the page to get overflow and the dropdown is getting focused on every scroll down. This happens only on firefox (installed version 113.0.1). 
adding screencast below

**How do you reproduce the problem?**
Please note that on sandbox this works as expected and only firefox is not
https://codesandbox.io/s/xenodochial-brook-ljcmvg?file=/index.js


**Expected behavior**
In case the dropdown is causing the page to overflow we should be able to see the bottom of the menu (as the chrome example I posted does)

**Is this issue blocking you?**
Not blocking me. My workaround is using Chrome for now 

**Screenshots**
firefox (note that I can't scroll to the bottom of the dropdown menu):

https://github.com/patternfly/patternfly-react/assets/67270715/154995b2-8ca7-4d8f-b6f4-9a1efc78f9bd

chrome (here everything works as expected):

https://github.com/patternfly/patternfly-react/assets/67270715/f1ee3eb1-2671-41b7-8cb6-ee8dea8c3237

**What is your environment?**
 - OS: fedora 36
 - Browser firefox
 - Version 103.0.1

**What is your product and what release date are you targeting?**

**Any other information?**
when the zoom is at 90% or lower this issue wasn't reproduceable for me, it was easier to reproduce on higher zoom like 110% and above
user: avivtur
issue_9289: state: open
title: Use the new JSX tranform
body: The React team [announced](https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html) a new way to transform JSX, which yields a couple of benefits:

- With the new transform, you can **use JSX without importing React**.
- Depending on your setup, its compiled output may **slightly improve the bundle size**.
- It will enable future improvements that **reduce the number of concepts** you need to learn React.
- There are some [performance improvements and simplifications](https://github.com/reactjs/rfcs/blob/createlement-rfc/text/0000-create-element-changes.md#motivation) that `React.createElement` does not allow.

This will also be required for future versions of React that will ship with the ECMAScript module syntax:

> In addition to cleaning up unused imports, this will also help you prepare for a future major version of React (not React 17) which will support ES Modules and not have a default export.

user: jonkoops
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_9251: state: open
title: Bug - [Drawer] - [examples give a11y errors with eslint a11y plugin]
body: error  `tabIndex` should only be declared on interactive elements  jsx-a11y/no-noninteractive-tabindex


tabIndex used as here https://patternfly-react-v5.surge.sh/components/drawer/#basic


user: KKoukiou
issue_9169: state: open
title: Popper - possibly add as a dependency
body: **Is this a new component or an extension of an existing one?**
Popper

**Describe the feature**
A README in our `helpers/Popper/thirdparty` directory mentions:

>- Delete the thirdparty folder and add them as dependencies to the package.json:
>`"react-popper": "2.2.3"`
>`"@popperjs/core": "2.4.2"`

Most likely not as part of this breaking change, but is this something we'd want to look into for a future major release? An alternative would be https://github.com/patternfly/patternfly-react/issues/9089 which would involve just updating our thirdparty code (possibly).
user: thatblindgeye
labels: breaking change :boom:: this change requires a major release and has API changes.
issue_9127: state: open
title: Update outdated dependencies (post v5)
body: The dependencies needing updated post v5:

<details>
  <summary>`yarn outdated`</summary>

```log
@fortawesome/free-brands-svg-icons   5.14.0         5.15.4         6.4.0    @patternfly/react-icons        devDependencies https://fontawesome.com                                                          
@fortawesome/free-regular-svg-icons  5.14.0         5.15.4         6.4.0    @patternfly/react-icons        devDependencies https://fontawesome.com                                                          
@fortawesome/free-solid-svg-icons    5.14.0         5.15.4         6.4.0    @patternfly/react-icons        devDependencies https://fontawesome.com                                                          
@patternfly/documentation-framework  2.0.0-alpha.39 2.0.0-alpha.41 1.10.10  @patternfly/react-docs         devDependencies                                                                                  
@pmmmwh/react-refresh-webpack-plugin 0.5.7          0.5.7          0.5.10   demo-app-ts                    devDependencies https://github.com/pmmmwh/react-refresh-webpack-plugin#readme                    
@rollup/plugin-commonjs              24.1.0         24.1.0         25.0.0   @patternfly/react-core         devDependencies https://github.com/rollup/plugins/tree/master/packages/commonjs/#readme          
@testing-library/react               13.4.0         13.4.0         14.0.0   @patternfly/react-lerna-root   devDependencies https://github.com/testing-library/react-testing-library#readme                  
@types/lodash                        4.14.157       4.14.194       4.14.194 @patternfly/react-charts       devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/lodash      
@types/react                         18.0.17        18.2.6         18.2.6   @patternfly/react-lerna-root   devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react       
@types/react                         18.0.17        18.2.6         18.2.6   demo-app-ts                    devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react       
@types/react-dom                     18.0.6         18.2.4         18.2.4   @patternfly/react-lerna-root   devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-dom   
@types/react-dom                     18.0.6         18.2.4         18.2.4   demo-app-ts                    devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-dom   
@typescript-eslint/eslint-plugin     5.59.5         5.59.6         5.59.6   @patternfly/react-lerna-root   devDependencies https://github.com/typescript-eslint/typescript-eslint#readme                    
@typescript-eslint/parser            5.59.5         5.59.6         5.59.6   @patternfly/react-lerna-root   devDependencies https://github.com/typescript-eslint/typescript-eslint#readme                    
babel-jest                           27.2.5         27.5.1         29.5.0   @patternfly/react-lerna-root   devDependencies https://github.com/facebook/jest#readme                                          
camel-case                           3.0.0          3.0.0          4.1.2    @patternfly/react-styles       devDependencies https://github.com/blakeembrey/change-case/tree/master/packages/camel-case#readme
classnames                           2.3.1          2.3.2          2.3.2    demo-app-ts                    devDependencies https://github.com/JedWatson/classnames#readme                                   
clean-webpack-plugin                 3.0.0          3.0.0          4.0.0    demo-app-ts                    devDependencies https://github.com/johnagan/clean-webpack-plugin                                 
concurrently                         7.6.0          7.6.0          8.0.1    @patternfly/react-lerna-root   devDependencies https://github.com/open-cli-tools/concurrently#readme                            
copy-webpack-plugin                  6.1.0          6.4.1          11.0.0   demo-app-ts                    devDependencies https://github.com/webpack-contrib/copy-webpack-plugin                           
css                                  2.2.4          2.2.4          3.0.0    @patternfly/react-charts       devDependencies https://github.com/reworkcss/css#readme                                          
css                                  2.2.4          2.2.4          3.0.0    @patternfly/react-core         devDependencies https://github.com/reworkcss/css#readme                                          
css                                  2.2.4          2.2.4          3.0.0    @patternfly/react-styles       devDependencies https://github.com/reworkcss/css#readme                                          
css                                  2.2.4          2.2.4          3.0.0    @patternfly/react-tokens       devDependencies https://github.com/reworkcss/css#readme                                          
css-loader                           4.3.0          4.3.0          6.7.3    demo-app-ts                    devDependencies https://github.com/webpack-contrib/css-loader                                    
cypress                              8.4.1          8.7.0          12.12.0  @patternfly/react-integration  devDependencies https://github.com/cypress-io/cypress                                            
eslint-plugin-standard               4.1.0          4.1.0          5.0.0    eslint-plugin-patternfly-react dependencies    https://github.com/standard/eslint-plugin-standard#readme                        
file-loader                          6.1.0          6.2.0          6.2.0    demo-app-ts                    devDependencies https://github.com/webpack-contrib/file-loader                                   
fork-ts-checker-webpack-plugin       6.5.2          6.5.2          8.0.0    demo-app-ts                    devDependencies https://github.com/TypeStrong/fork-ts-checker-webpack-plugin#readme              
glob                                 9.3.0          9.3.5          10.2.4   @patternfly/react-lerna-root   devDependencies https://github.com/isaacs/node-glob#readme                                       
glob                                 7.1.6          7.2.3          10.2.4   @patternfly/react-charts       devDependencies https://github.com/isaacs/node-glob#readme                                       
glob                                 7.1.6          7.2.3          10.2.4   @patternfly/react-core         devDependencies https://github.com/isaacs/node-glob#readme                                       
glob                                 7.1.6          7.2.3          10.2.4   @patternfly/react-icons        devDependencies https://github.com/isaacs/node-glob#readme                                       
glob                                 7.1.6          7.2.3          10.2.4   @patternfly/react-styles       devDependencies https://github.com/isaacs/node-glob#readme                                       
glob                                 7.1.6          7.2.3          10.2.4   @patternfly/react-tokens       devDependencies https://github.com/isaacs/node-glob#readme                                       
html-webpack-plugin                  5.5.0          5.5.1          5.5.1    demo-app-ts                    devDependencies https://github.com/jantimon/html-webpack-plugin                                  
husky                                4.3.8          4.3.8          8.0.3    @patternfly/react-lerna-root   devDependencies https://typicode.github.io/husky                                                 
jest                                 27.2.5         27.2.5         29.5.0   @patternfly/react-lerna-root   devDependencies https://jestjs.io/                                                               
jest-cli                             27.2.5         27.2.5         29.5.0   @patternfly/react-lerna-root   devDependencies https://jestjs.io/                                                               
jsdom                                15.2.1         15.2.1         22.0.0   @patternfly/react-styles       devDependencies https://github.com/jsdom/jsdom#readme                                            
lerna                                6.4.1          6.6.2          6.6.2    @patternfly/react-lerna-root   devDependencies https://lerna.js.org                                                             
local-web-server                     2.6.1          2.6.1          5.3.0    demo-app-ts                    devDependencies https://github.com/lwsjs/local-web-server#readme                                 
lodash                               4.17.20        4.17.21        4.17.21  @patternfly/react-charts       dependencies    https://lodash.com/                                                              
lodash                               4.17.20        4.17.21        4.17.21  @patternfly/react-table        dependencies    https://lodash.com/                                                              
mini-css-extract-plugin              0.11.2         0.11.3         2.7.5    demo-app-ts                    devDependencies https://github.com/webpack-contrib/mini-css-extract-plugin                       
monaco-editor-webpack-plugin         2.1.0          2.1.0          7.0.1    @patternfly/react-integration  devDependencies https://github.com/microsoft/monaco-editor#readme                                
react-hot-loader                     4.13.0         4.13.0         4.13.1   demo-app-ts                    devDependencies https://github.com/gaearon/react-hot-loader                                      
react-monaco-editor                  0.51.0         0.51.0         0.52.0   @patternfly/react-integration  devDependencies https://github.com/react-monaco-editor/react-monaco-editor                       
react-refresh-typescript             2.0.7          2.0.7          2.0.9    demo-app-ts                    devDependencies https://github.com/Jack-Works/react-refresh-transformer#readme                   
react-router                         5.3.3          5.3.4          6.11.1   demo-app-ts                    dependencies    https://github.com/remix-run/react-router#readme                                 
react-router-dom                     5.3.3          5.3.4          6.11.1   demo-app-ts                    dependencies    https://github.com/remix-run/react-router#readme                                 
rimraf                               2.7.1          2.7.1          5.0.0    @patternfly/react-charts       devDependencies https://github.com/isaacs/rimraf#readme                                          
rimraf                               2.7.1          2.7.1          5.0.0    @patternfly/react-code-editor  devDependencies https://github.com/isaacs/rimraf#readme                                          
rimraf                               3.0.2          3.0.2          5.0.0    @patternfly/react-core         devDependencies https://github.com/isaacs/rimraf#readme                                          
rimraf                               2.7.1          2.7.1          5.0.0    @patternfly/react-docs         devDependencies https://github.com/isaacs/rimraf#readme                                          
rimraf                               2.7.1          2.7.1          5.0.0    @patternfly/react-icons        devDependencies https://github.com/isaacs/rimraf#readme                                          
rimraf                               2.7.1          2.7.1          5.0.0    @patternfly/react-styles       devDependencies https://github.com/isaacs/rimraf#readme                                          
rimraf                               2.7.1          2.7.1          5.0.0    @patternfly/react-table        devDependencies https://github.com/isaacs/rimraf#readme                                          
rimraf                               2.7.1          2.7.1          5.0.0    @patternfly/react-tokens       devDependencies https://github.com/isaacs/rimraf#readme                                          
rollup                               3.21.7         3.21.8         3.21.8   @patternfly/react-core         devDependencies https://rollupjs.org/                                                            
style-loader                         3.3.1          3.3.1          3.3.2    demo-app-ts                    devDependencies https://github.com/webpack-contrib/style-loader                                  
ts-loader                            8.4.0          8.4.0          9.4.2    demo-app-ts                    devDependencies https://github.com/TypeStrong/ts-loader                                          
ts-loader                            8.4.0          8.4.0          9.4.2    @patternfly/react-integration  devDependencies https://github.com/TypeStrong/ts-loader                                          
typescript                           4.7.4          4.9.5          5.0.4    @patternfly/react-lerna-root   devDependencies https://www.typescriptlang.org/                                                  
typescript                           4.7.4          4.9.5          5.0.4    @patternfly/react-charts       devDependencies https://www.typescriptlang.org/                                                  
typescript                           4.7.4          4.9.5          5.0.4    @patternfly/react-code-editor  devDependencies https://www.typescriptlang.org/                                                  
typescript                           4.7.4          4.9.5          5.0.4    @patternfly/react-core         devDependencies https://www.typescriptlang.org/                                                  
typescript                           4.7.4          4.9.5          5.0.4    @patternfly/react-icons        devDependencies https://www.typescriptlang.org/                                                  
typescript                           4.7.4          4.9.5          5.0.4    demo-app-ts                    devDependencies https://www.typescriptlang.org/                                                  
typescript                           4.7.4          4.9.5          5.0.4    @patternfly/react-integration  devDependencies https://www.typescriptlang.org/                                                  
typescript                           4.7.4          4.9.5          5.0.4    @patternfly/react-styles       devDependencies https://www.typescriptlang.org/                                                  
typescript                           4.7.4          4.9.5          5.0.4    @patternfly/react-table        devDependencies https://www.typescriptlang.org/                                                  
url-loader                           4.1.0          4.1.1          4.1.1    demo-app-ts                    devDependencies https://github.com/webpack-contrib/url-loader                                    
webpack                              5.73.0         5.73.0         5.82.1   demo-app-ts                    devDependencies https://github.com/webpack/webpack                                               
webpack                              4.44.1         4.46.0         5.82.1   @patternfly/react-integration  devDependencies https://github.com/webpack/webpack                                               
webpack-cli                          4.10.0         4.10.0         5.1.1    demo-app-ts                    devDependencies https://github.com/webpack/webpack-cli/tree/master/packages/webpack-cli          
webpack-dev-server                   4.9.3          4.9.3          4.15.0   demo-app-ts                    devDependencies https://github.com/webpack/webpack-dev-server#readme  
```

</details>
```[tasklist]
### Tasks
```

user: nicolethoen
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_9111: state: open
title: Checkbox/Radio - allow flow content as body
body: **Is this a new component or an extension of an existing one?**

Existing components, Checkbox and Radio.

**Describe the feature**

To allow [flow content](https://developer.mozilla.org/en-US/docs/Web/HTML/Content_categories#flow_content) for their `body` prop. Currently it's wrapped in a `span` element, which only admits [phrasing content](https://developer.mozilla.org/en-US/docs/Web/HTML/Content_categories#phrasing_content).

**Are there visuals for this feature? If applicable, please include examples for each state and for varying widths**

I don't think so.

**Any other information?**

* The `body` being wrapped in a `span` was requested in a review because the [Radio `isLabelWrapped`](https://www.patternfly.org/v4/components/radio#label-wraps) prop. See https://github.com/patternfly/patternfly-react/pull/5559#pullrequestreview-617903386
* I've created a ~silly~ weird example of a Checkbox using flow content in its body, just for illustrating a possible use case of a React node returning a `div`. See https://codesandbox.io/s/weird-patternfly-checkbox-91mzqq or the screenshot uploaded below

  <details>
  <summary>Click to show/hide a screenshot of the output from the Codesanbox pasted above</summary>

  ---
 
  ![A screenshot of two weird checkboxes with three flexbox columns each one in their bodies](https://github.com/patternfly/patternfly-react/assets/1691872/330aae79-75f4-45ce-91b2-edc332720933)

  </details>

* If the change isn't possible beacuse the benefit does not pay off complicating the code for these components, at least it would be nice to mention in the [documentation](https://www.patternfly.org/v4/components/checkbox) that  the expected React.ReactNode must return phrasing content only
user: dgdavid
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_9089: state: open
title: Popper - investigate alternate solution for positioning bug
body: **Is this a new component or an extension of an existing one?**
Popper

**Describe the feature**
Followup to #9088, which provides a temporary solution to a positioning bug with Popper. This issue may only require investigating into the 3rd party libraries that our Popper is based on to see if there is something else that may resolve the positioning issue.

user: thatblindgeye
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_9013: state: open
title: navigator.clipboard is ONLY available in secure contexts (HTTPS)
body: Ref: https://github.com/patternfly/patternfly-react/blob/ce1afc78845fba2fd75a62f3ed440b289b4d5b56/packages/react-core/src/components/ClipboardCopy/ClipboardCopy.tsx#LL14C1-L14C1

Therefore the `clipboardCopyFunc` can only be used in secured contexts. The code above doesn't work for pages served under HTTP for instance. (Bear in mind that this works properly for pages served locally under HTTP, e.g. http://localhost/...).

Please check out [this article](https://web.dev/async-clipboard/#security-and-permissions) for more info.
user: jkilzi
issue_8983: state: open
title: Bug - Tooltip - aria prop not working correctly with VO
body: **Describe the problem**
A clear and concise description of the problem. Which components are affected?
There is a bug in the "On icon with dynamic content" demo of `Tooltip`. http://patternfly-react-v5.surge.sh/components/tooltip#on-icon-with-dynamic-content

In the docs it is mentioned that you can pass `aria` to prevent the content from being read twice by a screenreader, however the content is still getting read twice in the example if you test with VO.

**How do you reproduce the problem?**

Go to the link above and navigate to the tooltip with VO.

**Expected behavior**
A clear and concise description of the expected behavior.

Tooltip content is read only once.

**Is this issue blocking you?**
List the workaround if there is one.
Not blocking, found workaround by setting `role="none"` on `Tooltip`

**What is your product?**
Found in ODH


user: jenny-s51
issue_8980: state: open
title: Bug - docs should not use @reach/router
body: importing Link from @reach/router is not React 18 compatible. We don't want it as a patternfly-react dependency anymore
We will want to use (probably) react-router-dom or something more modern/react 18 compatible.

It's currently used in at least the following component examples/demos:

- Button examples
- Label examples (& demos in integration)
- Masthead examples & demos
- ComposableMenu demos
- App launcher examples
- Dropdown examples
user: nicolethoen
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_8971: state: open
title: Table - ActionsColumn: a11y violation in actions menu when triggering modal
body: **Is this a new component or an extension of an existing one?**

ActionsColumn

**Describe the feature**

When testing in ODH, this a11y violation was raised: https://docs.deque.com/issue-help/1.0.0/en/focus-modal-not-returned

If the consumer toggles a modal open via the actions menu kebab, the kebab is closed but it should remain open and the triggering element should retain focus when the modal is closed. 

**The focus MUST be purposely moved or set (via JavaScript) onto the appropriate element when the user's action requires a change of context or location for effective keyboard or touch interaction.**

**The focus MUST NOT become lost or reset to the top of the page, except when loading or re-loading a page.**

TODO: Update the ActionsColumn dropdown logic to support the isOpen state on the kebab when an item is selected.


user: jenny-s51
issue_8964: state: open
title: Bug - Table sort - Can't add aria-label
body: **Describe the problem**
It's not possible to add `aria-label` in Table sorts, so I can't use semantic syntax. If I'm a user who needs a screen reader to sort some data by name, for example, I just listen "name button" and not something with a better description.

**Expected behavior**
If I'm a user who needs a screen reader, when clicking in a button I should listen to a descriptive message about the functionality of the button, for accessibility purpose. So, when I have data inside a Table and I want to sort that data, I need to listen to a clear message.

**Is this issue blocking you?**
No

**What is your environment?**
 - RHEL 8.6
 - Browser Chrome

**What is your product and what release date are you targeting?**
consoledot

user: andressadotpy
issue_8933: state: open
title: Menu - MenuSearch component name
body: `MenuSearch` which is just a wrapper for any search or inputs (typically `MenuSearchInput`) could be renamed to something more generic like `MenuHeader`.
user: kmcfaul
labels: breaking change :boom:: this change requires a major release and has API changes.
DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_8850: state: open
title: Bug - [Masthead] - MastheadBrand icons is reloaded
body: Every time the Dropdown component is toggled, the MastheadBrand/MastheadBrand Image component is reloaded. This issue only occurs when using MastheadBrand with an icon router link. The affected components are Dropdown and MastheadBrand/MastheadBrand Image.

**How do you reproduce the problem?**

Use MastheadBrand with an icon router link.
Toggle the Dropdown component.
Notice that the MastheadBrand/MastheadBrand Image component is reloaded each time the Dropdown state changes.
Expected behavior
The MastheadBrand/MastheadBrand Image component should not be reloaded when toggling the Dropdown component, regardless of whether MastheadBrand is used with an icon router link or not.

Is this issue blocking you?
This issue may not be critical, but it can affect the performance of the website/application. A workaround could be to use MastheadBrand without an icon router link.

**Code Sandbox:**
https://26rvq2.csb.app/

Open and close the menu bar on the right, and observe the logo. The issue is observed in specific versions of browsers only.

Screenshots
N/A

**What is your environment?**

OS: MacOS 13.2
Browser: Version 111.0.5563.64 (Official Build) (x86_64)
Version: ^4.276.6
user: sumitridhal
issue_8740: state: open
title: Tooltip- rename trigger prop
body: Currently the `trigger` prop is very similar to Popper's `trigger` prop, can it's purpose can be confused with `triggerRef` that will exist for Popper. Since it's an action trigger for the tooltip, maybe it can be renamed to `triggerEvent` instead.
user: kmcfaul
labels: breaking change :boom:: this change requires a major release and has API changes.
DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_8717: state: open
title: Linting - modernize set of linting rules
body: PatternFly-React defines the standard set of linting rules used both by PatternFly React core libraries and PatternFly Extensions.  These should be reviewed to ensure the set of rules are up to date with industry React development standards.  

1) Identify a set of industry standards (is there a set of best practices for linting rules that can be followed?)
2) Introduce new rules and a plan for the React libraries to adopt these
user: dgutride
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_8635: state: open
title: Page - change notificationDrawer props to be more generic
body: re: https://github.com/patternfly/patternfly-react/issues/8541#issuecomment-1384624420

There are currently a props on the `<Page>` component (`notificationDrawer` and `isNotificationDrawerExpanded`) that attach a drawer to the page. AFAIK there is no requirement to use a notification drawer there - the props just update the page to support a drawer that appears over the main content area. Assuming we don't want to limit that use of a drawer in the page to notification drawer only, I wonder if it makes sense to rename those props to something more generic so it's clear it can be used for any sort of drawer content.

cc @mcarrano @mceledonia @tlabaj 

user: mcoker
labels: breaking change :boom:: this change requires a major release and has API changes.
DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_8594: state: open
title: Wrong example shown on forms page
body: https://www.patternfly.org/v4/components/form#validated

The example for "validated" is showing an "invalidated" state. 

(hi!)
user: ajacobs21e
issue_8561: state: open
title: Toolbar - support for gap
body: Placeholder work for core PR - https://github.com/patternfly/patternfly/pull/5243

This may end up being part of https://github.com/patternfly/patternfly-react/issues/8397
user: mcoker
labels: breaking change :boom:: this change requires a major release and has API changes.
DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_8542: state: open
title: Tile - deprecate Tile component
body: Tile can be seen as a specialized version of the Card. Tiles are always clickable and have a compact layout. Deprecate Tile in favor of using clickable cards.


user: mcarrano
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_8541: state: open
title: Bug - Page/Drawer - PageSection in DrawerBody has an incorrect height
body: **Describe the problem**
I am trying to build a page, which has several clickable cards on it, and when you click on the card, there will be a drawer panel shown on the right side. However, when implementing this, I find some issues with the page height. See the example below for the details.

**How do you reproduce the problem?**
I created a code sandbox example here: https://codesandbox.io/s/vigorous-bohr-ydpp8d?file=/index.tsx
I try to put a drawer in a `Page` component and set the `PageSection` in the `DrawerContentBody`, however, the `DrawerContentBody` is not flex display, which will make the grey background page section not take up the entire page height. So I use the `Flex` layout provided by PatternFly. However, another bug comes, the page section will take up more height than it should take, which causes the page to scrollable.

**Expected behavior**
The page section will take up the full page height when there is no enough card, and will be scrollable when there are a lot of cards.

**Is this issue blocking you?**
I can create some custom styles to avoid this. However, I still want to use only PF to build the application, avoid making any custom styles.

**Screenshots**
See the example.

**What is your environment?**
 - OS: [e.g. iOS]
 - Browser [e.g. chrome, safari]
 - Version [e.g. 22]

**What is your product and what release date are you targeting?**
ODH/RHODS

**Any other information?**
I am not sure whether it's permitted to put `PageSection` into `DrawerContentBody` by design. If not, what's the workable way to implement this feature? Is there any component that can provide me with a grey background on which I can put a lot of cards?

user: DaoDaoNoCode
issue_8534: state: open
title: Drawer - automatically manage focus when drawer is opened/closed
body: Follow up for core issue https://github.com/patternfly/patternfly/issues/5319
A more consistent solution than was used to fix https://github.com/patternfly/patternfly-react/issues/8394

move the close button to the top of the drawer body rather than the end.

The modal component automatically places focus on the first interactable element in the modal when it is opened. 
In the case of the Drawer, that should be the close button by default. 
If the close button is not provided, then it should be the first interactable element in the drawer.
If there are no interactable elements, focus should be placed on the drawer body.

Like the modal, this should happen automatically for the drawer, unless overridden by the consumer.

When the drawer is closed, focus should be returned to the drawer toggle - or at least, the props needed for the consumer to implement this focus management should be exposed. All related examples/demos should be updated to use this behavior (including the wizard with drawer)


user: nicolethoen
labels: breaking change :boom:: this change requires a major release and has API changes.
Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_8506: state: open
title: Bug - Expandable section - Update docs to highlight expandable sections as headings
body: **Describe the problem**
Whenever the text of the button for an expandable section introduces/summarizes the content it describes, the toggle is also functioning as a heading. In such cases, the user should use the detached variant of the expandable section and wrap the toggle button in a heading element.

This use case should be called out in the examples/documentation.

**Expected behavior**
The correct way to implement this is to surround the button with the heading tag.  For example:

```
      <h3>
          <button type="button" aria-expanded="true" class="accordion-trigger" aria-controls="sect1" id="accordion1id">
             See more important stuff
              <span class="accordion-icon"></span>
          </button>
      </h3>
        <div id="sect1" role="region" aria-labelledby="accordion1id" class="accordion-panel">
            This is the important stuff that is hidden/shown by the button above
        </div>
```

The `toggleText`, `'toggleTextCollapsed`, and `toggleTextExpanded` are typed as strings, but you can use the `toggleContent` to send a heading

For example:
```
 <ExpandableSection
      toggleContent={
        <h2>I am a heading</h2>
      }
      onToggle={onToggle}
      isExpanded={isExpanded}
    >
      This content is visible only when the component is expanded.
    </ExpandableSection>
```

The problem is that the heading tag, in this case, an h2, is a child of the button.  This will lead many assistive technologies to tread the heading as presentational so they aren't picked up by the heading list. See: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role#all_descendants_are_presentational

The OCM code base uses numerous expandable sections and new work will be adding additional expanding sections in the near future. 

**Any other information?**

I'm an expert in mediating accessibility issues.  Please feel free to contact me via the Internal Red Hat slack if you have questions or need assistance.
user: kdoberst
issue_8499: state: open
title: Wizard next - add more documentation to examples
body: follow up to this PR comment: https://github.com/patternfly/patternfly-react/pull/8422#pullrequestreview-1238101512

Wizard next examples need more explanation regarding purpose and implementation details
user: nicolethoen
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_8483: state: open
title: Bug - Tabs - Tabs do not behave as expected for keyboard users (accessibility)
body: **Describe the problem**
When navigating the tab list via keyboard, unexpected items have focus and standard expected keyboard keys are not functional. 

See: https://www.w3.org/WAI/ARIA/apg/patterns/tabpanel/
For the W3C standards on how the tab widget is expected to function when navigating via the keyboard.  

**How do you reproduce the problem?**
Any PF tab list and keyboard will due.  See https://www.patternfly.org/v4/components/tabs

**Expected behavior**
Summarizing from: https://www.w3.org/WAI/ARIA/apg/patterns/tabpanel/

When I use the keyboard tab key and select the tab list, I shall be able to use the arrow keys (up/down for vertical tabs and right/left for horizontal tabs) to move between (aka select) different tabs. 

When I click on the keyboard tab key again, I expect to have the tab panel (aka the tab content) to be selected.

**Current behavior**
When I use the keyboard tab key and select the tab list, the arrow keys are non-functional.

When I currently have the tab list selected and I click on the keyboard tab key, I am unexpectantly brought to the next tab instead of the content.

**Is this issue blocking you?**
Technically you _can_ get to the content, but only in non-standard and unexpected ways. Beyond being unexpected and having to somehow know how the tabs work, navigating via the keyboard as currently implemented is time-consuming and confusing vs the standard approach.  I would consider this a major accessibility issue.

**What is your environment?**
 - OS: [e.g. iOS]: Any (I tested using a macbook pro using OS 11.7.1)
 - Browser [e.g. chrome, safari]: Any (I tested using chrome 108.0.5359.124 )

**What is your product and what release date are you targeting?**
OCM

**Any other information?**

I'm an expert in mediating accessibility issues, and I fixed numerous tab sets in my day.  Please feel free to contact me via the Internal Red Hat slack if you have questions or need assistance.

user: kdoberst
issue_8463: state: open
title: CodeEditor - Un-indent code shortcut
body: **Is this a new component or an extension of an existing one?**
This is a new feature for the existing `CodeEditor` component

**Describe the feature**
I've noticed that the `CodeEditor` component [adds a command](https://github.com/patternfly/patternfly-react/blob/fbbc405bd078b4be09afc735f06ea5e924a15870/packages/react-code-editor/src/components/CodeEditor/CodeEditor.tsx#L384) for the `shift-tab` shortcut that focuses the monaco-editor parent element.

We're going to use `CodeEditor` for YAML code in our project. Indentation is important for YAML because it's how it denotes nesting. Usually `shift-tab` is the common shortcut used within IDEs to un-indent code. 

I was wondering if it could make sense to let users configure the `CodeEditor` to not override the default `shift-tab` behavior.

It's still possible to remove indentation by deleting tabs manually but I'm afraid that not being able to use `shift-tab` could be annoying in the long run.

**Are there visuals for this feature? If applicable, please include examples for each state and for varying widths**
Not applicable


user: kelvah
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_8459: state: open
title: Use proper zindex for components that use popper
body: Placeholder for work in https://github.com/patternfly/patternfly/issues/4973

Components that use popper can reference CSS tokens for z-index values that should maintain the proper stacking order.
user: mcoker
labels: breaking change :boom:: this change requires a major release and has API changes.
issue_8458: state: open
title: Tabs - support use of vertical tabs in sidebar component
body: Placeholder for core work in https://github.com/patternfly/patternfly/issues/3915

Not sure if there will be work needed here, but a placeholder in case there is.

user: mcoker
labels: breaking change :boom:: this change requires a major release and has API changes.
issue_8451: state: open
title: Form controls (text input, form select, textarea) - investigate status icon structure
body: Placeholder for core work in https://github.com/patternfly/patternfly/issues/2702
user: mcoker
issue_8450: state: open
title: Notification badge - update to use menu toggle
body: placeholder for core work - https://github.com/patternfly/patternfly/issues/5129
user: mcoker
labels: breaking change :boom:: this change requires a major release and has API changes.
issue_8445: state: open
title: Bug - Popover - Translation is not behaving correctly (noticeable in datepicker)
body: **Describe the problem**
If you open the Calendar view by clicking multiple times on the calendar icon on the DatePicker component, you will see that the calendar popover position changes.

**How do you reproduce the problem?**

Go on https://www.patternfly.org/v4/components/date-picker/ an click multiple times on the calendar icon
See screenshot

**Expected behavior**
Popover position should not change

**Screenshots**

![Screen Recording 2022-12-14 at 17 28 20](https://user-images.githubusercontent.com/118891193/207653652-a64cc8ee-eddf-4f0c-9191-80a8ec90c89f.gif)


**What is your environment?**
 - OS: Os X
 - Browser Chrome
 - Version 108.0.5359.98 (Official Build) (x86_64)

**What is your product and what release date are you targeting?**

**Any other information?**

If you look at the style of the popover between click, you will see the translate3d values changing 

popover style on the first click: `opacity: 1; transition: opacity 300ms cubic-bezier(0.54, 1.5, 0.38, 1.11) 0s; position: absolute; inset: 0px auto auto 0px; z-index: 9999; transform: translate3d(217.5px, -152.5px, 0px);`
popover style on the second click: `opacity: 1; transition: opacity 300ms cubic-bezier(0.54, 1.5, 0.38, 1.11) 0s; position: absolute; inset: 0px auto auto 0px; transform: translate3d(0px, 61px, 0px); z-index: 9999;`
third: `opacity: 1; transition: opacity 300ms cubic-bezier(0.54, 1.5, 0.38, 1.11) 0s; position: absolute; inset: 0px auto auto 0px; transform: translate3d(217.5px, 0px, 0px); z-index: 9999;`
fourth: `opacity: 1; transition: opacity 300ms cubic-bezier(0.54, 1.5, 0.38, 1.11) 0s; position: absolute; inset: 0px auto auto 0px; transform: translate3d(0px, 61px, 0px); z-index: 9999;`
user: rh-gvincent
issue_8418: state: open
title: Drilldown class updates to match core
body: placeholder for https://github.com/patternfly/patternfly/issues/5274

It would probably be useful to introduce classes on the drilldown menu that give us finer control over targeting/styling elements based on their state as the menu is modified.

This comment provides an example of the intended update.

https://github.com/patternfly/patternfly/pull/5271#issue-1471825828

cc @thatblindgeye 
user: mcoker
labels: breaking change :boom:: this change requires a major release and has API changes.
issue_8417: state: open
title: Calendar month - updates from padding change
body: Placeholder for https://github.com/patternfly/patternfly/issues/5272

We're removing the calendar month component's built-in padding. This will most likely involve updating any place the calendar month is used to make sure the thing the calendar month is in provides padding for the calendar. eg, remove `hasNoPadding` from the [datepicker popover](https://github.com/patternfly/patternfly-react/blob/16dc61cc8c2e8ee43522c388c638290d34bbb20b/packages/react-core/src/components/DatePicker/DatePicker.tsx#L244).
user: mcoker
labels: breaking change :boom:: this change requires a major release and has API changes.
issue_8416: state: open
title: Pagination : Rename internal sub components so they are name spaced
body: Rename the following Pagination sub components so they are name spaced. Prepend them with "Pagination":

- `Navigation`  to `PaginationNavigation` 
- `OptionsToggle` to `PaginationOptionsToggle`

Note:  This is not a breaking change since these sub components are not exported.
user: tlabaj
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_8400: state: open
title: List test revamp
user: wise-king-sullyman
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_8318: state: open
title: Bug - component examples with search input missing tabbable clear button
body: **Describe the problem**
A clear and concise description of the problem. Which components are affected?

Related: #8040, #8293

From @thatblindgeye 's review comments [here](https://github.com/patternfly/patternfly-react/pull/8040#pullrequestreview-1117532817) and [here](https://github.com/patternfly/patternfly-react/pull/8293#pullrequestreview-1159021177).

- [ ] Dual List Selector: [Basic with Search](https://patternfly-react-v5.surge.sh/components/dual-list-selector#basic-with-search), [Complex Items with Actions 
](https://patternfly-react-v5.surge.sh/components/dual-list-selector#using-more-complex-options-with-actions), [With tree](https://patternfly-react-v5.surge.sh/components/dual-list-selector#with-tree)
- [ ] Menu: [Drilldown with inline filter](https://patternfly-react-v5.surge.sh/components/menus/menu#with-drilldown-and-inline-filter), [Filtering with search input](https://patternfly-react-v5.surge.sh/components/menus/menu#filtering-with-search-input)
- [ ] Toolbar: [Toolber items](https://patternfly-react-v5.surge.sh/components/toolbar#toolbar-items), [Sticky toolbar](https://patternfly-react-v5.surge.sh/components/toolbar#sticky-toolbar)
- [ ] DataList: [Expandable content in toolbar](https://patternfly-react-v5.surge.sh/components/data-list/react-demos#expandable-control-in-toolbar)
- [ ] Masthead: [utilities and user dropdowns demo](https://patternfly-react-v5.surge.sh/components/masthead/react-demos#masthead-with-utilities-and-user-dropdown-menu)

**Expected behavior**
A clear and concise description of the expected behavior.
Search Inputs should have tabbable clear button.

user: jenny-s51
issue_8294: state: open
title: Update webpack to the latest version
body: It's a major version bump
Related to https://github.com/patternfly/patternfly-react/issues/8003
user: nicolethoen
labels: breaking change :boom:: this change requires a major release and has API changes.
issue_8271: state: open
title: "Disable Style Injection" wiki
body: The wiki below describes using `null-loader` as the recommended solution to disable style injection for webpack.
https://github.com/patternfly/patternfly-react/wiki/Disabling-Style-Injection-with-Webpack

Unfortunately, Red Hat recently flagged `loader-utils` (a dependency of `null-loader`) as having a security issue.

"CVE-2022-37599 loader-utils: regular expression denial of service in interpolateName.js"
https://issues.redhat.com/browse/COST-3158

Note that the `null-loader` package has been deprecated and its repo archived.
https://github.com/webpack-contrib/null-loader
user: dlabrecq
issue_8262: state: open
title: Text input, textarea, form select - add support for invalid modifier class
body: Placeholder for core work in https://github.com/patternfly/patternfly/issues/4384
user: mcoker
labels: breaking change :boom:: this change requires a major release and has API changes.
Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_8261: state: open
title: Menu - update to use panel for header/footer content
body: Placeholder for https://github.com/patternfly/patternfly/issues/5050
user: mcoker
labels: breaking change :boom:: this change requires a major release and has API changes.
Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_8259: state: open
title: Update form groups to use fieldset elements
body: Placeholder for core work in https://github.com/patternfly/patternfly/issues/4893
user: mcoker
labels: breaking change :boom:: this change requires a major release and has API changes.
Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_8257: state: open
title: Page - updates to support isWidthLimited by default
body: Placeholder for the work in https://github.com/patternfly/patternfly/issues/4851

At a minimum, there are markup differences between a non-`isWidthLimited` section and `isWidthLimited`. It would be good to have the markup be the same, and we may have sections be `isWidthLimited` by default.
user: mcoker
labels: breaking change :boom:: this change requires a major release and has API changes.
DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_8255: state: open
title: Tree view - allow for interactive component in node content
body: Placeholder for https://github.com/patternfly/pf-requests/issues/6

This work may need to be done in collaboration with core to make sure the keyboard a11y and anything else works as intended. cc @kmcfaul 
user: mcoker
labels: breaking change :boom:: this change requires a major release and has API changes.
DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_8252: state: open
title: Support for component animations
body: Placeholder for the core work in https://github.com/patternfly/patternfly/issues/4979

If the animations can be handled all in CSS, there may be no react work needed, but we may need to introduce things like event handlers to watch, for example, `transitionend` before removing an element from the DOM or adding/removing a class.
user: mcoker
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_8248: state: open
title: Input Components - Simplify Interface by handling FormGroup internally
body: Labels and inputs in html are hooked together by ID.

```html
<label for="username">Enter your username:</label>
<input id="username" />
```

In PF4 to get a label on an input requires a FormGroup.

```
<FormGroup
    id="user-form-group"
    fieldId="user"
    label="User"
    helperText="User help text"
    isRequired
    validated={error ? 'error' : undefined}
    helperTextInvalid={error}
>
    <TextInput
        id="user"
        type="text"
        aria-describedby="user-form-group"
        isRequired
        validated={error ? 'error' : undefined}
        placeholder="Enter user"
        value={user}
        onChange={onChange}
    />
</FormGroup>
```

It make for a streamlined developer experience if that logic could be hidden from the developer. On a input component, if a label is provided, then the component could handle all the logic internally.

```
<TextInput
    id="user"
    label="User"
    helper="User help text"
    type="text"
    required
    placeholder="Enter user"
    value={user}
    onChange={onChange}
    error={error}
/>
```
user: jamestalton
labels: breaking change :boom:: this change requires a major release and has API changes.
DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_8178: state: open
title: Toolbar - parity with core features
body: Looking at the toolbar CSS, I noticed a few things. Note that I didn't go through everything in detail, but that may be a good for whoever picks this up if they're comfortable. 

* there are `.pf-m-wrap` and `.pf-m-nowrap` modifier classes that support breakpoint suffixes to control the flex wrapping behavior of `.pf-c-toolbar__group` and `.pf-c-toolbar__content-section`. I couldn't find support for these modifiers in the react component, but maybe I missed them? https://github.com/patternfly/patternfly/blob/e362c95792e234592911881cb3c818177c023fd5/src/patternfly/components/Toolbar/toolbar.scss#L497-L506
* `<ToolbarContent>` supports `alignment`, but I do not see any CSS support for `.pf-m-align-[left/right]` for `.pf-c-toolbar__content`
* The `<ToolbarItem>` supports a `width` prop that allows a custom CSS `width` with breakpoint support by setting [--pf-c-toolbar__item--Width[-breakpoint]](https://github.com/patternfly/patternfly-react/blob/b44f6c31e0ab822af9626fd16912d4eb6ba01f3e/packages/react-core/src/components/Toolbar/ToolbarItem.tsx#L112), which is awesome. The CSS also supports the same for `min-width` via [--pf-c-toolbar__item--MinWidth[-breakpoint]](https://github.com/patternfly/patternfly/blob/e362c95792e234592911881cb3c818177c023fd5/src/patternfly/components/Toolbar/toolbar.scss#L272) - I don't see that in the react component. A use case for that is something like `width: 80%; min-width: 300px;` for something you want to consume 80% of the parent, but never shrink below `300px`.
user: mcoker
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_8130: state: open
title: DashboardWrapper demo updates
body: re: https://github.com/patternfly/patternfly-react/pull/7927#pullrequestreview-1125650784

I think we want the vertical nav's `aria-label` to be "Global", otherwise the rotor reads this as "Nav navigation". "Global" is the default, so if we want to update, you could remove this entirely. This also matches the `<PageToggleButton>`'s aria-label, and those labels should probably match.

https://github.com/patternfly/patternfly-react/blob/22fc7d8e8189ef2da0eb483a8c35c4c0e2be3807/packages/react-core/src/demos/examples/DashboardWrapper.js#L73

https://github.com/patternfly/patternfly-react/blob/22fc7d8e8189ef2da0eb483a8c35c4c0e2be3807/packages/react-core/src/demos/examples/DashboardHeader.js#L220

---

A bunch of the demos have body text that references the Overpass font and some specific font styles that aren't relevant and may change (and be incorrect) as styles change over time. Just in general, I'd say we should review the body text of demos/examples and make sure we don't have other stuff like this. Here's a list of the places I found that reference the overpass text

```
packages/react-core/src//demos/Nav.md:                Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/Nav.md:                Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/Nav.md:                Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/Nav.md:                Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/Nav.md:                Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/Nav.md:                Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/Nav.md:                Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/Nav.md:                Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/Nav.md:                Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/PrimaryDetail.md:              Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/PrimaryDetail.md:              Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/PrimaryDetail.md:              Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/PrimaryDetail.md:              Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/PrimaryDetail.md:              Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/Banner.md:                Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/Banner.md:                    Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/examples/BackToTop/BackToTopNameDemo.tsx:              Body text should be Overpass Regular at 16px.It should have leading of 24px because <br />
packages/react-core/src//demos/NotificationDrawer/NotificationDrawer.md:                Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-core/src//demos/NotificationDrawer/NotificationDrawer.md:                Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
packages/react-table/src//docs/examples/ComposableTableStickyToolbar.tsx:              Body text should be Overpass Regular at 16px. It should have leading of 24px because <br />
```

---

This page section should be `isWidthLimited`, or maybe some mechanism to add/remove that depending on what else is on the page (like if other page sections aren't width limited?), though I'm not sure if there is ever a use case where this wouldn't be width limited. I guess it doesn't matter here since the text isn't very long, but if more content is added, it will keep it from spanning the whole viewport.

https://github.com/patternfly/patternfly-react/blob/22fc7d8e8189ef2da0eb483a8c35c4c0e2be3807/packages/react-core/src/demos/examples/DashboardWrapper.js#L29-L34
user: mcoker
issue_8078: state: open
title: Modal: Deprecate modal
body: Deprecate the modal

- Move the Modal code to the deprecated directory (`react-core\src\deprecated\`). The documentation would show up under a "React deprecated" tab on the Modal page  of the website.
- Promote the "next Modal" to our default Modal component by moving it to `react-core\src\components\`.  

related to https://github.com/patternfly/patternfly-react/issues/8076
user: tlabaj
labels: breaking change :boom:: this change requires a major release and has API changes.
DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_8059: state: open
title: Label group - live region/a way to convey a label was added
body: **Is this a new component or an extension of an existing one?**
Label group

**Describe the feature**
Currently when a label is added via the examples/demos where a label can be added, there's no indication that a label was successfully added when interacting via VoiceOver. 

A live region on the label group when `addLabelControl` is passed in would help resolve this, but may be verbose if there are a lot of labels (each label would get read out loud, not just the newly created one).

**Are there visuals for this feature? If applicable, please include examples for each state and for varying widths**
Include screenshots or links to Marvel or other mockups.
N/A

**Any other information?**
N/A
user: thatblindgeye
issue_8026: state: open
title: Ship packages as ESM only
body: **Is this a new component or an extension of an existing one?**
This applies to all packages in the PatternFly React repository.

**Describe the feature**
Instead of shipping PatternFly React packages with a bunch of different module systems (UMD, CommonJS, etc). All packages would be shipped only in the standardized ECMAScript module format.
user: jonkoops
labels: breaking change :boom:: this change requires a major release and has API changes.
DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_7932: state: open
title: chore: clean up exported helpers
body: Some of the exported helpers should only be used internally to PF.  

- Let's reassess what we export
- Find a way to document functionality on the website that should be exported.
cc @evwilkin 
user: tlabaj
labels: breaking change :boom:: this change requires a major release and has API changes.
Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_7923: state: open
title: Bug - Tooltips on Charts - Tooltips for non-Latin character code pages are too narrow
body: **Describe the problem**
By default the `@patternfly/react-charts` chart tooltips use the same text width estimation as is used in the Victory charts. This estimation works ok for ASCII characters, but underestimate sizes for other non-Latin character code pages.

**How do you reproduce the problem?**
Have a chart tooltip is any non-Latin character language.  Japanese is a good example.

**Expected behavior**
The tooltips for Latin character languages have their text's width estimated well, but for non-Latin character language (such as Japanese), the text width is vastly underestimated.

**Is this issue blocking you?**
No, but could be very common in non-Latin languages.  It was first detected in a Japanese translation.

The workaround used was to force the tooltip to a constant width wide enough to display the tooltip in every translation.

For example, in (https://github.com/oVirt/ovirt-engine-ui-extensions/blob/0642c73c45dc084bd841e1928884dd1fa61bb0b0/src/components/patternfly/DonutChart.js#L40-L52), the `ChartTooltip`'s `flyoutWidth` is set to a constant value:
```jsx
      <ChartDonutUtilization
        title={donutChartText}
        subTitle={donutChartSubtitle}
        themeColor={ChartThemeColor.green}
        labelComponent={<ChartTooltip flyoutWidth={180} />}
        data={{ x: 'Capacity', y: percentUsed * 100 }}
        labels={({ datum }) => datum.x ? usedLabel : availableLabel}
        thresholds={colors}
        events={[{ target: 'data', eventHandlers: { onClick: onDataClick } }]}
        height={200}
        width={200}
        padding={{ top: 15 }}
      />
```

**Screenshots**

Example 1:
![screenshot-1](https://user-images.githubusercontent.com/3985964/187990700-1c3b56ae-4920-4774-b12b-11a514117f19.png)

Example 2:
![image-2022-03-24-20-50-57-694](https://user-images.githubusercontent.com/3985964/187990709-e8591d30-08a0-44c7-8d0e-9d9be14d7b36.png)
**What is your environment?**
 - OS: Any
 - Browser: Any
 - Version: ` "@patternfly/react-charts": "^6.74.3"`

**What is your product and what release date are you targeting?**
oVirt

**Any other information?**
See:
  - https://issues.redhat.com/browse/RHV-45439
  - https://github.com/oVirt/ovirt-engine-ui-extensions/pull/74
user: sjd78
issue_7871: state: open
title: Bug - NumberInput: values/validation status not announced to assistive tech on update
body: **Describe the problem**
Followup to #7806. Relevant comment chains: https://github.com/patternfly/patternfly-react/pull/7806#pullrequestreview-1077847330, https://github.com/patternfly/patternfly-react/pull/7806#pullrequestreview-1077854208, and https://github.com/patternfly/patternfly-react/pull/7806#issuecomment-1220611457

**How do you reproduce the problem?**
1. Go to [Number input](https://www.patternfly.org/v4/components/number-input)
2. Turn on VoiceOver or another screen reader
3. Use keyboard to update the input (either via the +/- buttons or within the input itself)
4. Notice the value does not get announced
    - In Chromium browsers, updating via buttons or via the input itself does not trigger an announcement. In Firefox and Safari, updating via the input announces the new value but updating via the buttons does not.

**Expected behavior**
The new value of the input and/or the validation status is announced to assistive tech

**Is this issue blocking you?**
N/A

**Screenshots**
N/A

**What is your environment?**
N/A

**What is your product and what release date are you targeting?**
N/A

**Any other information?**
N/A
user: thatblindgeye
labels: PF4: React issues for the PF4 core effort
issue_7832: state: open
title: [Chore] - [Replace babble with TSC (TypeScript transpiler) ]
body: Dependency:
Consider replacing babble with TSC transpiler.


user: tlabaj
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_7776: state: open
title: Bug - Table - at mobile widths, expandable rows have non-focusable scrollable content
body: This needs to be fixed in the legacy and composable table expandable row examples.

<img width="1079" alt="Screen Shot 2022-07-29 at 12 38 15 PM" src="https://user-images.githubusercontent.com/26305082/181815013-5d8e5972-c0f2-4e70-bfe3-5f2707a88ad0.png">

<img width="519" alt="Screen Shot 2022-07-29 at 12 37 59 PM" src="https://user-images.githubusercontent.com/26305082/181815023-93702f7c-43af-471b-a410-dc15bb82fe56.png">

after fixing this issue, we should also remove the config which ignores the rule 'scrollable-region-focusable' in the `react-docs/patternfly-a11y.config.js`
user: nicolethoen
issue_7745: state: open
title: Bug - Table - hoverable example invalid markup and selection not announced on navigation
body: **Describe the problem**
Followup to #7732 

The [hoverable selectable Table example](https://www.patternfly.org/v4/components/table#composable-row-click-handler-hoverable--selected-rows) throws the following warning in the dev environment:

`Warning: validateDOMNesting(...): <output> cannot appear as a child of <tbody>`

Additionally, due to the way screen readers navigate tables (by cell rather than by row), the row that is selected only gets announced when a row is selected via a cell. Using Tab to navigate between rows (as the table caption instructs) does announce whether the row is selected, but it only announces the `aria-label` and not the content of the row.

Some possible alternatives:

- Add a hidden input to each row, similar to the implementation seen in [Data list selectable rows example](https://www.patternfly.org/v4/components/data-list#selectable-rows). To avoid invalid markup, I believe this might require having an empty column similar to the table examples that use visible radio inputs.
- Add a hidden input to the first cell of a row, and add styling so that when the radio input has focus it looks like the row has focus.
- Move the current `output` element to the first `<td>` element of a row

**How do you reproduce the problem?**
Navigate the [Hoverable selectable table example](https://www.patternfly.org/v4/components/table#composable-row-click-handler-hoverable--selected-rows) with a screen reader

**Expected behavior**
Markup is valid, and users can be notified whether the current row is selected as best as possible

**Is this issue blocking you?**
No

**Screenshots**
N/A

**What is your environment?**
N/A

**What is your product and what release date are you targeting?**
N/A

**Any other information?**
N/A
user: thatblindgeye
issue_7690: state: open
title: Docs: open issues & questions
body: Capturing some questions and things to decide on regarding documentation to improve consistency.

General documentation:
- `KeyboardHandler` and `Popper` are exported and should be included in our docs, but are not currently.
consider documenting the utilities under the website "Utility".  We could have React and CSS sub categories. 

- `CSS variables` section could be moved out of each page and into a separate tab to cut down on page length (and demo pages are not consistent on whether this section is included)
- Would it be worth introducing another sub-level into the sidebar navigation to group similar components together (ex. grouping `Textarea`, `Text input`, `Text input group` into a new folder `Text` under `Components`) or would that be too many levels of drill-in?
- Should `Legacy` use a badge/banner similar to `Beta` to further visually distinguish components/examples instead of using text? This would also cut down on example title length. 
Open org issue and design issue for the deprecated badge.  open design issue for deprecated banner.

Example-related: 
- Data sets in component examples sometimes use practical, real world-like data (Dell, Samsung...) vs. descriptive data (Option 1, Option 2...), sometimes swap data set types between examples on the same component page, and sometimes analogous examples between react+html do not match data set types. We might want to pick one type of data, or form data sets relevant to each component and be consistent within a component page for react and html.
components should be reviewed for content in examples/demos before it is promoted from Beta.
Open issue to update example/demos for real world vs descriptive data.

- Examples with common features repeat phrases in their titles and could be grouped under a subheader instead (ex. `AlertGroup` has “Singular dynamic alert group”, “Singular dynamic alert group with overflow message”, and “Multiple dynamic alert group” examples)
- Examples use flag modifier elements inconsistently - sometimes included above vs. below the example, sometimes uses checkbox vs. button vs. radio. Tooltip has a large table of options modifying a single example.
- Example titles between react and core are inconsistent for analogous examples. There is also inconsistency in the term used for basic use case examples (between "basic", "default", and "simple").
- Should example titles use punctuation? Most example titles do not which make the several that do stand out


user: kmcfaul
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_7594: state: open
title: chore: update component unit tests to meet new standards with RTL
body: **Describe the issue. What is the expected and unexpected behavior?**
This Epic will track the work of updating the test suites for our components to meet our [new RTL testing standards and methodology](https://github.com/patternfly/patternfly-react/wiki/React-Testing-Library-Basics,-Best-Practices,-and-Guidelines).  Please create issues as you pick up tasking.

NOTE: As part of this effort console statements should be mocked in revamped tests rather than actually printing the console

- [x] #7605
- [x] #7665
- [x] #7670
- [x] #9524
- [x] #7835
- [x] #7812
- [x] #7813
- [x] #8189
- [x] #9525
- [x] #7994
- [x] #8094
- [x] #9526
- [x] #7860
- [x] #9527
- [ ] #9528
- [x] #9529
- [x] #9530
- [x] #9531
- [x] #9532
- [x] #9533
- [ ] #9534
- [x] #9634
- [ ] #9685
- [x] #9673
- [x] #9684
- [ ] #9686
- [x] #7964
- [ ] #9688
- [ ] #9689
- [ ] File upload
- [ ] File upload - multiple
- [ ] Form
- [ ] Form control
- [ ] Form select
- [x] #9760
- [x] #7616
- [ ] Inline edit
- [ ] Input group
- [ ] Jump links
- [ ] Label
- [ ] Label group
- [ ] #8400
- [ ] Login page
- [ ] Masthead
- [ ] Menu
- [ ] Menu toggle
- [ ] Modal
- [ ] Navigation
- [ ] Notification Badge
- [ ] Number input
- [ ] Overflow menu
- [ ] Page
- [ ] Pagination
- [x] #8247
- [ ] Popover
- [ ] Progress
- [x] #8345
- [ ] Radio
- [ ] Search input
- [x] #8302
- [ ] Simple list
- [ ] Skeleton
- [ ] Skip to content
- [ ] Slider
- [ ] Spinner
- [ ] Switch
- [ ] Tab content
- [x] #8173
- [ ] Text
- [x] #7976
- [ ] Text input
- [x] #7169 
- [ ] Tile
- [ ] Time picker
- [x] #8007
- [ ] Toggle group
- [x] #7687
- [x] #9768
- [x] #7643

The following components are expected to change significantly in the near future. Updates to their tests should be delayed until those changes are completed.

- [ ] About modal
- [ ] Card
- [ ] Composable table
- [ ] Drawer
- [ ] Dual list selector
- [ ] Notification drawer
- [ ] Toolbar
- [ ] Wizard
user: wise-king-sullyman
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_7554: state: open
title: Bug - Skip to content - focus remains at top of page in demos
body: **Describe the problem**
Followup based on comment https://github.com/patternfly/patternfly-react/pull/7520#issuecomment-1154088525

The skip to content component has a bug in demos where when you click it, focus remains at the top of the page/the page does not scroll to the main content.

**How do you reproduce the problem?**
1. Go to [skip to content React demo](https://www.patternfly.org/v4/components/skip-to-content/react/basic/)
2. Press Tab to place focus on the Skip to content button, press Enter, then press Tab again. Notice that focus goes back to the skip button, and the page did not scroll to the main content.
    - If you click anywhere on the page first then follow the steps above, the page does scroll to the main content, but focus still remains at the top of the page when pressing Tab again
4.  Go to [bulk select table demo](https://www.patternfly.org/v4/components/table/react-demos/bulk-select/#main-content-page-layout-default-nav) and repeat Step 2, and notice the same behavior.

**Expected behavior**
The skip to content in React demos should have the same behavior as seen in the [skip to content HTML demo](https://www.patternfly.org/v4/components/skip-to-content/html/basic/)


user: thatblindgeye
issue_7471: state: open
title: Bug - Table  - Refactor Column Management with Draggable demo 
body: **Describe the problem**
A clear and concise description of the problem. Which components are affected?

> @jenny-s51 This looks great, but there seems to be a bug with column reordering via drag & drop. If I reorder columns and then click Save, upon returning to the table, it's empty.

_Originally posted by @mcarrano in https://github.com/patternfly/patternfly-react/pull/7446#pullrequestreview-986229584_

@mcarrano noticed this bug upon review of #7446 ... this bug already existed in the column management draggable demo. Looks like we're using `DataList`'s deprecated onDrag API here, along with the deprecated `itemOrder` prop.

In order to fix this bug, we need to refactor this demo to use `DragDrop` with `DataList` here.


user: jenny-s51
issue_7467: state: open
title: CodeEditor - testing is needed for interactions with React Dropzone and the Monaco Editor
body: As mentioned in #7450 the Code Editor is lacking in test coverage based on our newly determined testing guidelines.

I anticipate the most difficult part of this issue will likely be determining how we should test certain aspects surrounding the Monaco Editor and React Dropzone libraries that we use.

Monaco seems to do something that makes entering text in its editor difficult using RTL, and React Dropzone has functions (such as its `open` function) which I'm not sure how would be best to test.
user: wise-king-sullyman
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_7415: state: open
title: docs: demo page updates
body: <!-- What changes are being made? Please link the issue being addressed. -->
**What**: Draft for https://github.com/patternfly/patternfly-org/issues/2935

First pass for how an updated demo page with templated content may function. Adds a generic blurb at the top of the demo page, and boilerplate structure for component lists.

"Card view" and "Composable menu" demo pages are updated currently to test and showcase changes.

Open questions:
- Should subcomponents of components be included in the overall component list or should the list only correlate to docs pages?
- How should component lists be shown? Currently it is using LabelGroup/Label to create a visual list, which allows the differentiation between components and layouts.
- Should components and layouts be separate or should they be in the same list? (See "Card view" demo page for layout example)
- Does using LabelGroup to denote components make the sentence blurb indicating a list of components redundant? Should the boilerplate sentence be removed?
- Should PF icons that are imported be called out?


user: kmcfaul
issue_7384: state: open
title: Table demos - improve table data and interactions
body: **Is this a new component or an extension of an existing one?**
What is the existing component, if any?
Table

**Describe the feature**
A clear and concise description of the new feature. What is the expected behavior?
some of that table demos have pagination components that do not match the data in the table (e.g. pagination says there are 4 pages of data and there are only 5 rows of data in the table.  Let's create some data to be used in all our table examples that would allow us to wire up the pagination to work as expected.  All demos should use the composable table.

This task should be completed as part of this epic:
- [x] #7795
- [x] #7685
- [x] #7855
- [x] #7991
- [x] #7882
- [x] Table: Update sticky header demo data
- [ ] Table: Update compound expansion demo data
- [x] #8066
- [x] #8065
- [x] #8079

user: tlabaj
labels: PF4: React issues for the PF4 core effort
Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_7287: state: open
title: Dependencies are quite outdated sometimes
body: Running `yarn outdated` in the root of the project yields quite some outdated dependencies:

<details>
  <summary>yarn outdated</summary>

  ```log
  @babel/core                               7.6.4    7.17.9   7.17.9   @patternfly/react-lerna-root             devDependencies https://babel.dev/docs/en/next/babel-core                                             
  @babel/plugin-proposal-class-properties   7.5.5    7.16.7   7.16.7   @patternfly/react-lerna-root             devDependencies https://babel.dev/docs/en/next/babel-plugin-proposal-class-properties                 
  @babel/plugin-proposal-decorators         7.8.3    7.17.9   7.17.9   @patternfly/react-lerna-root             devDependencies https://babel.dev/docs/en/next/babel-plugin-proposal-decorators                       
  @babel/plugin-proposal-object-rest-spread 7.6.2    7.17.3   7.17.3   @patternfly/react-lerna-root             devDependencies https://babel.dev/docs/en/next/babel-plugin-proposal-object-rest-spread               
  @babel/plugin-proposal-optional-chaining  7.11.0   7.16.7   7.16.7   @patternfly/react-lerna-root             devDependencies https://babel.dev/docs/en/next/babel-plugin-proposal-optional-chaining                
  @babel/preset-env                         7.6.3    7.16.11  7.16.11  @patternfly/react-lerna-root             devDependencies https://babel.dev/docs/en/next/babel-preset-env                                       
  @babel/preset-react                       7.6.3    7.16.7   7.16.7   @patternfly/react-lerna-root             devDependencies https://babel.dev/docs/en/next/babel-preset-react                                     
  @babel/preset-typescript                  7.10.4   7.16.7   7.16.7   @patternfly/react-lerna-root             devDependencies https://babel.dev/docs/en/next/babel-preset-typescript                                
  @fortawesome/free-brands-svg-icons        5.14.0   5.15.4   6.1.1    @patternfly/react-icons                  devDependencies https://fontawesome.com                                                               
  @fortawesome/free-regular-svg-icons       5.14.0   5.15.4   6.1.1    @patternfly/react-icons                  devDependencies https://fontawesome.com                                                               
  @fortawesome/free-solid-svg-icons         5.14.0   5.15.4   6.1.1    @patternfly/react-icons                  devDependencies https://fontawesome.com                                                               
  @novnc/novnc                              1.2.0    1.3.0    1.3.0    @patternfly/react-console                dependencies    https://github.com/novnc/noVNC                                                        
  @octokit/rest                             16.43.2  16.43.2  18.12.0  @patternfly/react-lerna-root             devDependencies https://github.com/octokit/rest.js#readme                                             
  @rollup/plugin-commonjs                   21.0.0   21.1.0   21.1.0   @patternfly/react-core                   devDependencies https://github.com/rollup/plugins/tree/master/packages/commonjs/#readme               
  @rollup/plugin-node-resolve               13.0.5   13.2.1   13.2.1   @patternfly/react-core                   devDependencies https://github.com/rollup/plugins/tree/master/packages/node-resolve/#readme           
  @rollup/plugin-replace                    3.0.0    3.1.0    4.0.0    @patternfly/react-core                   devDependencies https://github.com/rollup/plugins/tree/master/packages/replace#readme                 
  @testing-library/jest-dom                 5.16.2   5.16.4   5.16.4   @patternfly/react-lerna-root             devDependencies https://github.com/testing-library/jest-dom#readme                                    
  @testing-library/react                    12.1.2   12.1.5   13.1.1   @patternfly/react-lerna-root             devDependencies https://github.com/testing-library/react-testing-library#readme                       
  @testing-library/user-event               13.5.0   13.5.0   14.1.1   @patternfly/react-lerna-root             devDependencies https://github.com/testing-library/user-event#readme                                  
  @types/d3                                 5.7.2    5.16.4   7.1.0    @patternfly/react-topology               dependencies    https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/d3               
  @types/d3-force                           1.2.1    1.2.4    3.0.3    @patternfly/react-topology               dependencies    https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/d3-force         
  @types/dagre                              0.7.42   0.7.42   0.7.47   @patternfly/react-topology               dependencies    https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/dagre            
  @types/dom-helpers                        3.4.1    3.4.1    5.0.1    @patternfly/react-virtualized-extension  devDependencies                                                                                       
  @types/file-saver                         2.0.1    2.0.5    2.0.5    @patternfly/react-console                dependencies    https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/file-saver       
  @types/jest                               27.0.2   27.0.2   27.4.1   @patternfly/react-lerna-root             devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/jest             
  @types/lodash                             4.14.157 4.14.182 4.14.182 @patternfly/react-charts                 devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/lodash           
  @types/react                              17.0.34  17.0.44  18.0.6   @patternfly/react-lerna-root             devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react            
  @types/react                              17.0.34  17.0.44  18.0.6   @patternfly/react-docs                   devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react            
  @types/react                              17.0.34  17.0.44  18.0.6   demo-app-ts                              devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react            
  @types/react-dom                          17.0.11  17.0.15  18.0.2   @patternfly/react-lerna-root             devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-dom        
  @types/react-dom                          17.0.11  17.0.15  18.0.2   @patternfly/react-docs                   devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-dom        
  @types/react-dom                          17.0.11  17.0.15  18.0.2   demo-app-ts                              devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-dom        
  @types/react-measure                      2.0.6    2.0.8    2.0.8    @patternfly/react-topology               dependencies    https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-measure    
  @types/react-router-dom                   4.3.5    4.3.5    5.3.3    demo-app-ts                              devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-router-dom 
  @types/react-virtualized                  9.21.10  9.21.21  9.21.21  @patternfly/react-virtualized-extension  devDependencies https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-virtualized
  @typescript-eslint/eslint-plugin          4.4.1    4.33.0   5.20.0   @patternfly/react-lerna-root             devDependencies https://github.com/typescript-eslint/typescript-eslint#readme                         
  @typescript-eslint/parser                 4.4.1    4.33.0   5.20.0   @patternfly/react-lerna-root             devDependencies https://github.com/typescript-eslint/typescript-eslint#readme                         
  babel-eslint                              9.0.0    9.0.0    10.1.0   eslint-plugin-patternfly-react           dependencies    https://github.com/babel/babel-eslint                                                 
  babel-jest                                27.2.5   27.5.1   27.5.1   @patternfly/react-lerna-root             devDependencies https://github.com/facebook/jest#readme                                               
  camel-case                                3.0.0    3.0.0    4.1.2    @patternfly/react-styles                 devDependencies https://github.com/blakeembrey/change-case/tree/master/packages/camel-case#readme     
  clean-webpack-plugin                      3.0.0    3.0.0    4.0.0    demo-app-ts                              devDependencies https://github.com/johnagan/clean-webpack-plugin                                      
  concurrently                              5.3.0    5.3.0    7.1.0    @patternfly/react-lerna-root             devDependencies https://github.com/open-cli-tools/concurrently#readme                                 
  concurrently                              5.3.0    5.3.0    7.1.0    @patternfly/react-catalog-view-extension devDependencies https://github.com/open-cli-tools/concurrently#readme                                 
  copy-webpack-plugin                       6.1.0    6.4.1    10.2.4   demo-app-ts                              devDependencies https://github.com/webpack-contrib/copy-webpack-plugin                                
  css                                       2.2.4    2.2.4    3.0.0    @patternfly/react-charts                 devDependencies https://github.com/reworkcss/css#readme                                               
  css                                       2.2.4    2.2.4    3.0.0    @patternfly/react-core                   devDependencies https://github.com/reworkcss/css#readme                                               
  css                                       2.2.4    2.2.4    3.0.0    @patternfly/react-styles                 devDependencies https://github.com/reworkcss/css#readme                                               
  css                                       2.2.4    2.2.4    3.0.0    @patternfly/react-tokens                 devDependencies https://github.com/reworkcss/css#readme                                               
  css-loader                                4.3.0    4.3.0    6.7.1    demo-app-ts                              devDependencies https://github.com/webpack-contrib/css-loader                                         
  cypress                                   8.4.1    8.7.0    9.5.4    @patternfly/react-integration            devDependencies https://github.com/cypress-io/cypress                                                 
  d3                                        5.16.0   5.16.0   7.4.4    @patternfly/react-topology               dependencies    https://d3js.org                                                                      
  dagre                                     0.8.2    0.8.2    0.8.5    @patternfly/react-topology               dependencies    https://github.com/dagrejs/dagre#readme                                               
  eslint                                    7.11.0   7.32.0   8.13.0   @patternfly/react-lerna-root             devDependencies https://eslint.org                                                                    
  eslint-config-airbnb                      16.1.0   16.1.0   19.0.4   eslint-plugin-patternfly-react           dependencies    https://github.com/airbnb/javascript                                                  
  eslint-config-prettier                    2.10.0   2.10.0   8.5.0    eslint-plugin-patternfly-react           dependencies    https://github.com/prettier/eslint-config-prettier#readme                             
  eslint-config-standard                    11.0.0   11.0.0   17.0.0   eslint-plugin-patternfly-react           dependencies    https://github.com/standard/eslint-config-standard                                    
  eslint-config-standard-jsx                5.0.0    5.0.0    11.0.0   eslint-plugin-patternfly-react           dependencies    https://github.com/standard/eslint-config-standard-jsx                                
  eslint-config-standard-react              6.0.0    6.0.0    11.0.1   eslint-plugin-patternfly-react           dependencies    https://github.com/feross/eslint-config-standard-react                                
  eslint-plugin-import                      2.20.2   2.26.0   2.26.0   eslint-plugin-patternfly-react           dependencies    https://github.com/import-js/eslint-plugin-import                                     
  eslint-plugin-jest                        21.27.2  21.27.2  26.1.4   eslint-plugin-patternfly-react           dependencies    https://github.com/jest-community/eslint-plugin-jest#readme                           
  eslint-plugin-jsx-a11y                    6.2.3    6.5.1    6.5.1    eslint-plugin-patternfly-react           dependencies    https://github.com/jsx-eslint/eslint-plugin-jsx-a11y#readme                           
  eslint-plugin-markdown                    1.0.2    1.0.2    2.2.1    @patternfly/react-lerna-root             devDependencies https://github.com/eslint/eslint-plugin-markdown#readme                               
  eslint-plugin-node                        6.0.1    6.0.1    11.1.0   eslint-plugin-patternfly-react           dependencies    https://github.com/mysticatea/eslint-plugin-node#readme                               
  eslint-plugin-prettier                    3.1.4    3.4.1    4.0.0    @patternfly/react-lerna-root             devDependencies https://github.com/prettier/eslint-plugin-prettier#readme                             
  eslint-plugin-prettier                    2.7.0    2.7.0    4.0.0    eslint-plugin-patternfly-react           dependencies    https://github.com/prettier/eslint-plugin-prettier#readme                             
  eslint-plugin-promise                     3.8.0    3.8.0    6.0.0    eslint-plugin-patternfly-react           dependencies    https://github.com/xjamundx/eslint-plugin-promise                                     
  eslint-plugin-react                       7.21.4   7.29.4   7.29.4   @patternfly/react-lerna-root             devDependencies https://github.com/yannickcr/eslint-plugin-react                                      
  eslint-plugin-react                       7.19.0   7.29.4   7.29.4   eslint-plugin-patternfly-react           dependencies    https://github.com/yannickcr/eslint-plugin-react                                      
  eslint-plugin-react-hooks                 4.1.2    4.4.0    4.4.0    eslint-plugin-patternfly-react           dependencies    https://reactjs.org/                                                                  
  eslint-plugin-rulesdir                    0.1.0    0.1.0    0.2.1    eslint-plugin-patternfly-react           dependencies    https://github.com/not-an-aardvark/eslint-plugin-rulesdir#readme                      
  eslint-plugin-standard                    3.1.0    3.1.0    5.0.0    eslint-plugin-patternfly-react           dependencies    https://github.com/standard/eslint-plugin-standard#readme                             
  file-loader                               6.1.0    6.2.0    6.2.0    demo-app-ts                              devDependencies https://github.com/webpack-contrib/file-loader                                        
  file-saver                                1.3.8    1.3.8    2.0.5    @patternfly/react-console                dependencies    https://github.com/eligrey/FileSaver.js#readme                                        
  focus-trap                                6.2.2    6.2.2    6.8.0    @patternfly/react-core                   dependencies    https://github.com/focus-trap/focus-trap#readme                                       
  fs-extra                                  6.0.1    6.0.1    10.1.0   @patternfly/react-lerna-root             devDependencies https://github.com/jprichardson/node-fs-extra                                         
  fs-extra                                  6.0.1    6.0.1    10.1.0   @patternfly/react-charts                 devDependencies https://github.com/jprichardson/node-fs-extra                                         
  fs-extra                                  6.0.1    6.0.1    10.1.0   @patternfly/react-core                   devDependencies https://github.com/jprichardson/node-fs-extra                                         
  fs-extra                                  6.0.1    6.0.1    10.1.0   @patternfly/react-icons                  devDependencies https://github.com/jprichardson/node-fs-extra                                         
  fs-extra                                  6.0.1    6.0.1    10.1.0   @patternfly/react-styles                 devDependencies https://github.com/jprichardson/node-fs-extra                                         
  fs-extra                                  6.0.1    6.0.1    10.1.0   @patternfly/react-tokens                 devDependencies https://github.com/jprichardson/node-fs-extra                                         
  glob                                      7.1.6    7.2.0    8.0.1    @patternfly/react-lerna-root             devDependencies https://github.com/isaacs/node-glob#readme                                            
  glob                                      7.1.6    7.2.0    8.0.1    @patternfly/react-charts                 devDependencies https://github.com/isaacs/node-glob#readme                                            
  glob                                      7.1.6    7.2.0    8.0.1    @patternfly/react-core                   devDependencies https://github.com/isaacs/node-glob#readme                                            
  glob                                      7.1.6    7.2.0    8.0.1    @patternfly/react-icons                  devDependencies https://github.com/isaacs/node-glob#readme                                            
  glob                                      7.1.6    7.2.0    8.0.1    @patternfly/react-styles                 devDependencies https://github.com/isaacs/node-glob#readme                                            
  glob                                      7.1.6    7.2.0    8.0.1    @patternfly/react-tokens                 devDependencies https://github.com/isaacs/node-glob#readme                                            
  html-webpack-plugin                       4.4.1    4.5.2    5.5.0    demo-app-ts                              devDependencies https://github.com/jantimon/html-webpack-plugin                                       
  husky                                     4.3.0    4.3.8    7.0.4    @patternfly/react-lerna-root             devDependencies https://typicode.github.io/husky                                                      
  jest                                      27.2.5   27.2.5   27.5.1   @patternfly/react-lerna-root             devDependencies https://jestjs.io/                                                                    
  jest-cli                                  27.2.5   27.2.5   27.5.1   @patternfly/react-lerna-root             devDependencies https://jestjs.io/                                                                    
  jsdom                                     15.2.1   15.2.1   19.0.0   @patternfly/react-styles                 devDependencies https://github.com/jsdom/jsdom#readme                                                 
  lerna                                     3.22.1   3.22.1   4.0.0    @patternfly/react-lerna-root             devDependencies https://github.com/lerna/lerna#readme                                                 
  lint-staged                               10.4.2   10.5.4   12.4.0   @patternfly/react-lerna-root             devDependencies https://github.com/okonet/lint-staged#readme                                          
  local-web-server                          2.6.1    2.6.1    5.2.0    demo-app-ts                              devDependencies https://github.com/lwsjs/local-web-server#readme                                      
  lodash                                    4.17.20  4.17.21  4.17.21  @patternfly/react-charts                 dependencies    https://lodash.com/                                                                   
  lodash                                    4.17.20  4.17.21  4.17.21  @patternfly/react-table                  dependencies    https://lodash.com/                                                                   
  lodash                                    4.17.20  4.17.21  4.17.21  @patternfly/react-topology               dependencies    https://lodash.com/                                                                   
  memoize-one                               5.2.1    5.2.1    6.0.0    @patternfly/react-log-viewer             dependencies    https://github.com/alexreardon/memoize-one#readme                                     
  mini-css-extract-plugin                   0.11.2   0.11.3   2.6.0    demo-app-ts                              devDependencies https://github.com/webpack-contrib/mini-css-extract-plugin                            
  mobx                                      5.15.6   5.15.7   6.5.0    @patternfly/react-topology               dependencies    https://mobx.js.org/                                                                  
  mobx-react                                6.3.0    6.3.1    7.3.0    @patternfly/react-topology               dependencies    https://mobx.js.org                                                                   
  monaco-editor-webpack-plugin              2.1.0    2.1.0    7.0.1    @patternfly/react-integration            devDependencies https://github.com/microsoft/monaco-editor#readme                                     
  plop                                      2.7.4    2.7.6    3.0.5    @patternfly/react-lerna-root             devDependencies https://plopjs.com                                                                    
  point-in-svg-path                         1.0.1    1.0.2    1.0.2    @patternfly/react-topology               dependencies    https://github.com/maxnachlinger/point-in-svg-path                                    
  prettier                                  1.19.1   1.19.1   2.6.2    @patternfly/react-lerna-root             devDependencies https://prettier.io                                                                   
  react                                     17.0.1   17.0.2   18.0.0   @patternfly/react-lerna-root             devDependencies https://reactjs.org/                                                                  
  react                                     17.0.1   17.0.2   18.0.0   @patternfly/react-docs                   devDependencies https://reactjs.org/                                                                  
  react                                     17.0.1   17.0.2   18.0.0   demo-app-ts                              dependencies    https://reactjs.org/                                                                  
  react-dom                                 17.0.1   17.0.2   18.0.0   @patternfly/react-lerna-root             devDependencies https://reactjs.org/                                                                  
  react-dom                                 17.0.1   17.0.2   18.0.0   @patternfly/react-docs                   devDependencies https://reactjs.org/                                                                  
  react-dom                                 17.0.1   17.0.2   18.0.0   demo-app-ts                              dependencies    https://reactjs.org/                                                                  
  react-dropzone                            9.0.0    9.0.0    12.0.5   @patternfly/react-code-editor            dependencies    https://github.com/react-dropzone/react-dropzone                                      
  react-dropzone                            9.0.0    9.0.0    12.0.5   @patternfly/react-core                   dependencies    https://github.com/react-dropzone/react-dropzone                                      
  react-measure                             2.5.0    2.5.2    2.5.2    @patternfly/react-topology               dependencies    https://github.com/souporserious/react-measure                                        
  react-monaco-editor                       0.41.2   0.41.2   0.47.0   @patternfly/react-integration            devDependencies https://github.com/react-monaco-editor/react-monaco-editor                            
  react-router                              4.3.1    4.3.1    6.3.0    demo-app-ts                              dependencies    https://reactrouter.com/                                                              
  react-router-dom                          4.3.1    4.3.1    6.3.0    demo-app-ts                              dependencies    https://reactrouter.com/                                                              
  react-virtualized                         9.22.2   9.22.3   9.22.3   @patternfly/react-virtualized-extension  dependencies    https://github.com/bvaughn/react-virtualized                                          
  rimraf                                    2.7.1    2.7.1    3.0.2    @patternfly/react-catalog-view-extension devDependencies https://github.com/isaacs/rimraf#readme                                               
  rimraf                                    2.7.1    2.7.1    3.0.2    @patternfly/react-charts                 devDependencies https://github.com/isaacs/rimraf#readme                                               
  rimraf                                    2.7.1    2.7.1    3.0.2    @patternfly/react-code-editor            devDependencies https://github.com/isaacs/rimraf#readme                                               
  rimraf                                    2.7.1    2.7.1    3.0.2    @patternfly/react-console                devDependencies https://github.com/isaacs/rimraf#readme                                               
  rimraf                                    2.7.1    2.7.1    3.0.2    @patternfly/react-core                   devDependencies https://github.com/isaacs/rimraf#readme                                               
  rimraf                                    2.7.1    2.7.1    3.0.2    @patternfly/react-docs                   devDependencies https://github.com/isaacs/rimraf#readme                                               
  rimraf                                    2.7.1    2.7.1    3.0.2    @patternfly/react-icons                  devDependencies https://github.com/isaacs/rimraf#readme                                               
  rimraf                                    2.7.1    2.7.1    3.0.2    @patternfly/react-inline-edit-extension  devDependencies https://github.com/isaacs/rimraf#readme                                               
  rimraf                                    2.7.1    2.7.1    3.0.2    @patternfly/react-log-viewer             devDependencies https://github.com/isaacs/rimraf#readme                                               
  rimraf                                    2.7.1    2.7.1    3.0.2    @patternfly/react-styles                 devDependencies https://github.com/isaacs/rimraf#readme                                               
  rimraf                                    2.7.1    2.7.1    3.0.2    @patternfly/react-table                  devDependencies https://github.com/isaacs/rimraf#readme                                               
  rimraf                                    2.7.1    2.7.1    3.0.2    @patternfly/react-tokens                 devDependencies https://github.com/isaacs/rimraf#readme                                               
  rimraf                                    2.7.1    2.7.1    3.0.2    @patternfly/react-topology               devDependencies https://github.com/isaacs/rimraf#readme                                               
  rimraf                                    2.7.1    2.7.1    3.0.2    @patternfly/react-virtualized-extension  devDependencies https://github.com/isaacs/rimraf#readme                                               
  rollup                                    2.58.0   2.70.2   2.70.2   @patternfly/react-core                   devDependencies https://rollupjs.org/                                                                 
  sass                                      1.42.1   1.50.1   1.50.1   @patternfly/react-catalog-view-extension devDependencies https://github.com/sass/dart-sass                                                     
  shx                                       0.3.2    0.3.4    0.3.4    @patternfly/react-catalog-view-extension devDependencies https://github.com/shelljs/shx#readme                                                 
  shx                                       0.3.2    0.3.4    0.3.4    @patternfly/react-docs                   devDependencies https://github.com/shelljs/shx#readme                                                 
  surge                                     0.21.6   0.21.7   0.23.1   @patternfly/react-lerna-root             devDependencies https://github.com/sintaxi/surge#readme                                               
  theme-patternfly-org                      0.11.22  0.11.22  0.11.28  @patternfly/react-docs                   devDependencies                                                                                       
  tippy.js                                  5.1.2    5.1.2    6.3.7    @patternfly/react-core                   dependencies    https://atomiks.github.io/tippyjs/                                                    
  ts-loader                                 8.0.4    8.3.0    9.2.8    demo-app-ts                              devDependencies https://github.com/TypeStrong/ts-loader                                               
  ts-loader                                 8.0.17   8.3.0    9.2.8    @patternfly/react-integration            devDependencies https://github.com/TypeStrong/ts-loader                                               
  ts-patch                                  1.4.2    1.4.5    2.0.1    @patternfly/react-lerna-root             devDependencies https://github.com/nonara/ts-patch#readme                                             
  typescript                                4.3.5    4.6.3    4.6.3    @patternfly/react-lerna-root             devDependencies https://www.typescriptlang.org/                                                       
  typescript                                4.3.5    4.6.3    4.6.3    @patternfly/react-catalog-view-extension devDependencies https://www.typescriptlang.org/                                                       
  typescript                                4.3.5    4.6.3    4.6.3    @patternfly/react-charts                 devDependencies https://www.typescriptlang.org/                                                       
  typescript                                4.3.5    4.6.3    4.6.3    @patternfly/react-code-editor            devDependencies https://www.typescriptlang.org/                                                       
  typescript                                4.3.5    4.6.3    4.6.3    @patternfly/react-console                devDependencies https://www.typescriptlang.org/                                                       
  typescript                                4.3.5    4.6.3    4.6.3    @patternfly/react-core                   devDependencies https://www.typescriptlang.org/                                                       
  typescript                                4.3.5    4.6.3    4.6.3    @patternfly/react-icons                  devDependencies https://www.typescriptlang.org/                                                       
  typescript                                4.3.5    4.6.3    4.6.3    @patternfly/react-inline-edit-extension  devDependencies https://www.typescriptlang.org/                                                       
  typescript                                4.3.5    4.6.3    4.6.3    demo-app-ts                              devDependencies https://www.typescriptlang.org/                                                       
  typescript                                4.3.5    4.6.3    4.6.3    @patternfly/react-integration            devDependencies https://www.typescriptlang.org/                                                       
  typescript                                4.3.5    4.6.3    4.6.3    @patternfly/react-log-viewer             devDependencies https://www.typescriptlang.org/                                                       
  typescript                                4.3.5    4.6.3    4.6.3    @patternfly/react-styles                 devDependencies https://www.typescriptlang.org/                                                       
  typescript                                4.3.5    4.6.3    4.6.3    @patternfly/react-table                  devDependencies https://www.typescriptlang.org/                                                       
  typescript                                4.3.5    4.6.3    4.6.3    @patternfly/react-topology               devDependencies https://www.typescriptlang.org/                                                       
  typescript                                4.3.5    4.6.3    4.6.3    @patternfly/react-virtualized-extension  devDependencies https://www.typescriptlang.org/                                                       
  url-loader                                4.1.0    4.1.1    4.1.1    demo-app-ts                              devDependencies https://github.com/webpack-contrib/url-loader                                         
  victory-area                              36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  victory-axis                              36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  victory-bar                               36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  victory-chart                             36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  victory-core                              36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  victory-create-container                  36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  victory-group                             36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  victory-legend                            36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  victory-line                              36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  victory-pie                               36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  victory-scatter                           36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  victory-stack                             36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  victory-tooltip                           36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  victory-voronoi-container                 36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  victory-zoom-container                    36.2.1   36.3.2   36.3.2   @patternfly/react-charts                 dependencies    https://formidable.com/open-source/victory                                            
  webpack                                   4.44.1   4.46.0   5.72.0   demo-app-ts                              devDependencies https://github.com/webpack/webpack                                                    
  webpack                                   4.44.1   4.46.0   5.72.0   @patternfly/react-integration            devDependencies https://github.com/webpack/webpack                                                    
  webpack-cli                               3.3.12   3.3.12   4.9.2    demo-app-ts                              devDependencies https://github.com/webpack/webpack-cli/tree/master/packages/webpack-cli               
  xterm                                     4.9.0    4.18.0   4.18.0   @patternfly/react-console                dependencies    https://github.com/xtermjs/xterm.js#readme                                            
  xterm-addon-fit                           0.2.1    0.2.1    0.5.0    @patternfly/react-console                dependencies    https://github.com/xtermjs/xterm.js#readme         
  ```

</details>

Perhaps it's a good idea to set up [Dependabot](https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates) or expand [Renovate](https://docs.renovatebot.com/) to also upgrade other dependencies?

- [x] patternfly/patternfly-react#7314
- [x] patternfly/patternfly-react#7315
- [x] patternfly/patternfly#4816
- [ ] patternfly/patternfly#4817
- [x] patternfly/patternfly-react#7320
user: jonkoops
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_7214: state: open
title: [Skeleton] - [Add demo to match core]
body: **Is this a new component or an extension of an existing one?**
What is the existing component, if any?
Skeleton

**Describe the feature**
A clear and concise description of the new feature. What is the expected behavior?
Add a demo to match core
https://www.patternfly.org/v4/components/skeleton/html-demos


user: tlabaj
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_7209: state: open
title: [Masthead] - [Add missing Masthead demos]
body: **Is this a new component or an extension of an existing one?**
What is the existing component, if any?
Masthead

**Describe the feature**
A clear and concise description of the new feature. What is the expected behavior?

The following task should be completed to close this issue:

- [x] #7210 
- [ ] #6826



user: tlabaj
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_7142: state: open
title: Core - Add support for React 18
body: React 18 has been [released](https://reactjs.org/blog/2022/03/29/react-v18.html), code will have to be adjusted to that it is officially supported.

### Checklist
- [x] https://github.com/patternfly/patternfly-react/issues/6919
- [x] Update `@types/react` and `@types/react-dom` (https://github.com/DefinitelyTyped/DefinitelyTyped/pull/56210).
- [x] #7195
- [x] #7216
- [x] #7217
- [x] #7218
- [x] #7282
- [x] #7363
- [x] #7402
- [x] Add `PropsWithChildren` types to components with children
- [ ] Apply migrations from [upgrade guide](https://reactjs.org/blog/2022/03/08/react-18-upgrade-guide.html).
  - [x] #8027
  - [ ] https://github.com/patternfly/patternfly-org/pull/3203
- [ ]  Check for incompatible dependencies and upgrade if necessary.
  - [x] #7706
  - [x] #7826
  - [x] #8577
- [x] #7303
- [x] #7821
- [x] #7827
user: jonkoops
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_7010: state: open
title: Chore(docs): Add composable structure section and component descriptions to documentation
body: **Describe the issue. What is the expected and unexpected behavior?**
Consider adding a "General intended structure" section to documentation for more compassable components, and add descriptions for sub-components in the "Props" section to provide more details on their use-cases.

For sub-component descriptions, we should consider ensuring that any sub-components used in examples/exported for consumer use are added to the "Props" section. For example, Application Launcher has examples using ApplicationLauncherSeparator, but that is not included in the props section of the component page. **Note**: this will cause an issue for sub-components that do not export a props interface, as an empty table will be rendered to that section of the component page.

Additionally, we should align on when to include other components on a page's "Props" section. The Login Page component, for example, uses List and ListItem in some examples, but does not include the props table for them. The Alert Group component on the other hand includes the Alert props table.
 
e.g.
General intended structure
File upload - multiple is designed in a composable manner to maximize flexibility. The general intended component relationships are arranged similarly to:

<MultipleFileUpload>
  <MultipleFileUploadMain />
  <MultipleFileUploadStatus>
    <MultipleFileUploadStatusItem />
  </MultipleFileUploadStatus>
</MultipleFileUpload>

See #7603 for working examples


**Is this a bug or enhancement? If this issue is a bug, is this issue blocking you or is there a work-around?**
enhancement 

Needs only sub-component descriptions:
- [x] #7973 
- [x] #7978
- [x] #8105
- [ ] Wizard

Needs both "composable structure" and sub-component descriptions:
- [ ] Accordion
- [ ] Action list
- [ ] Alert group (currently the alert group page includes Alert specific components in the "Props" section)
- [x] Application launcher (partially composable)
- [ ] Breadcrumb
- [ ] Card
- [ ] Clipboard copy (currently the component page includes ClipboardCopyButton in the "Props" section, but the component isn't used in any examples. If we want to keep this, it may be worth considering whether any other sub-components should be exposed on all components)
- [ ] Chip group (currently the chip group page includes the Chip component in the "Props" section)
- [ ] Code block
- [x] Context selector
- [ ] Data list
- [ ] Description list
- [ ] Drag and drop (**wait for Nicole to provide feedback**)
- [ ] Drawer
- [ ] Dropdown (partially composable)
- [x] #7692
- [ ] Empty state
- [ ] Form
- [ ] Form select
- [ ] Helper text
- [ ] Hint
- [ ] Input group
- [ ] Jump links
- [ ] Label group (currently the label group page includes the Label component in its "Props" section)
- [ ] List
- [ ] Login page
- [ ] Masthead
- [ ] Menu
- [x] #7691 
- [ ] Navigation
- [ ] Notification drawer
- [ ] Options menu (partially composable)
- [ ] Overflow menu
- [ ] Page
- [ ] Panel
- [ ] Progress stepper
- [ ] Select (partially composable)
- [ ] Sidebar
- [ ] Simple list
- [ ] Table Composable (because of the different variants of a table, the structure section may need to be split up to several different ones)
- [x] Table Legacy (could arguably only require sub-component descriptions, but since examples show the `TableHeader` inside of `Table` it might be good to include some sort of "intended structure" section/mention)
- [ ] Tabs
- [ ] Text
- [ ] Text input group
- [ ] Toggle group
- [ ] Toolbar

user: tlabaj
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_7003: state: open
title: Dashboard demo
body: Create a Dashboard demo. Follow up on: https://github.com/patternfly/patternfly/pull/4721 Use real charts in place of image placeholders.
user: mcarrano
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_7000: state: open
title: Description list demo
body: Add a description list demo. Core PR: https://github.com/patternfly/patternfly/pull/4715

html demos on org: https://www.patternfly.org/components/description-list/html-demos
user: mcarrano
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_6889: state: open
title: Sticky toolbar demo
body: Want to add a new demo that shows the sticky toolbar used in a full page layout. See the design issue here: https://github.com/patternfly/patternfly-design/issues/1120
user: mcarrano
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_6826: state: open
title: Masthead: add demo that includes horizontal nav
body: Add a new demo that shows how to construct a masthead with a horizontal nav menu. See core PR here: https://github.com/patternfly/patternfly/pull/4617
user: mcarrano
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_6804: state: open
title: error when using npm to run install
body: when using npm 8 to execute `npm install` I get the following error:

```
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: eslint-plugin-patternfly-react@4.23.2
npm ERR! Found: eslint@8.7.0
npm ERR! node_modules/eslint
npm ERR!   peer eslint@">=5" from eslint-plugin-patternfly-react@4.23.2
npm ERR!   packages/eslint-plugin-patternfly-react
npm ERR!     eslint-plugin-patternfly-react@4.23.2
npm ERR!     node_modules/eslint-plugin-patternfly-react
npm ERR!       workspace packages/eslint-plugin-patternfly-react from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^4.9.0" from eslint-config-airbnb@16.1.0
npm ERR! node_modules/eslint-config-airbnb
npm ERR!   eslint-config-airbnb@"^16.1.0" from eslint-plugin-patternfly-react@4.23.2
npm ERR!   packages/eslint-plugin-patternfly-react
npm ERR!     eslint-plugin-patternfly-react@4.23.2
npm ERR!     node_modules/eslint-plugin-patternfly-react
npm ERR!       workspace packages/eslint-plugin-patternfly-react from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /Users/nthoen/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/nthoen/.npm/_logs/2022-01-17T13_07_09_970Z-debug-0.log
```

It seems - according to stack overflow that "When using npm 7, this comes up a lot because peer dependencies issues are treated as errors in version 7 whereas they were generally only warnings in version 6. Usually using --legacy-peer-deps makes it work with npm 7[+].”

When I run `npm install --legacy-peer-deps`, the install works with no errors.

It seems we might need to either readdress our dependencies, or update our README to suggest adding the flag or opting for yarn to perform the install
user: nicolethoen
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_6597: state: open
title: Add example: Composable Table with editable rows
user: nicolethoen
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_6531: state: open
title: TableComposable: refactor Draggable example to use a data-driven rather than config-driven approach, and possibly new DragDrop abstraction
body: Followup from #6168. In converting that example to TypeScript + Hooks, I left its logic mostly unmodified because it's possible we will need to rewrite it to use the new DragDrop components anyway. Just opening this so we remember to follow up, because that example is left using a different paradigm than the others rewritten in #6168.
user: mturley
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_6343: state: open
title: Integration tests are missing important focus management tests
body: We need working tests to evaluate focus management in two scenarios:

1. keyboard handling of focus in menu and menu like components
2. aria-disabled/disabled items - aria-disabled should be able to get browser focus but not handle click events

Previous attempts to test these features have been removed from the[ Dropdown cypress tests](https://github.com/patternfly/patternfly-react/pull/6340/files#diff-c223ffbdabeaf491f4a9023ad627ffaf74fdfce626b370641f8c317d2144b441) when cypress upgraded. Cypress does not like us clicking on disabled items or executing events on items that don't already have focus. 
user: nicolethoen
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_6246: state: open
title: Dependency Dashboard
body: This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.

## Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

 - [ ] <!-- rebase-branch=renovate/devdependencies -->[chore(deps): update devdependencies](../pull/9970) (`@babel/core`, `@babel/eslint-parser`, `@babel/plugin-proposal-decorators`, `@babel/preset-env`, `@patternfly/documentation-framework`, `@types/jest`, `@types/react`, `@types/react-dom`, `eslint`, `eslint-plugin-jest`, `prettier`)
 - [ ] <!-- rebase-branch=renovate/major-devdependencies -->[chore(deps): update devdependencies (major)](../pull/9898) (`@testing-library/jest-dom`, `@typescript-eslint/eslint-plugin`, `@typescript-eslint/parser`, `lint-staged`, `plop`, `rollup`, `ts-patch`)

## Detected dependencies

<details><summary>npm</summary>
<blockquote>

<details><summary>package.json</summary>

 - `@babel/core ^7.21.8`
 - `@babel/plugin-proposal-class-properties ^7.18.6`
 - `@babel/plugin-proposal-decorators ^7.21.0`
 - `@babel/plugin-proposal-object-rest-spread ^7.20.7`
 - `@babel/plugin-proposal-optional-chaining ^7.21.0`
 - `@babel/plugin-proposal-private-methods ^7.18.6`
 - `@babel/plugin-proposal-private-property-in-object ^7.21.0`
 - `@babel/preset-env ^7.21.5`
 - `@babel/preset-react ^7.18.6`
 - `@babel/preset-typescript ^7.21.5`
 - `@octokit/rest ^20.0.0`
 - `@testing-library/jest-dom ^5.16.5`
 - `@testing-library/user-event 14.5.2`
 - `@types/jest 29.5.11`
 - `@types/react ^18`
 - `@types/react-dom ^18`
 - `@typescript-eslint/eslint-plugin ^5.59.2`
 - `@typescript-eslint/parser ^5.59.2`
 - `eslint ^8.39.0`
 - `eslint-plugin-markdown ^3.0.0`
 - `eslint-plugin-prettier ^5.0.0`
 - `eslint-plugin-react ^7.32.2`
 - `eslint-plugin-testing-library ^6.1.0`
 - `fs-extra ^11.1.1`
 - `lint-staged ^14.0.0`
 - `mutation-observer ^1.0.3`
 - `plop ^3.1.2`
 - `prettier ^3.0.0`
 - `surge ^0.23.1`
 - `ts-patch ^2.1.0`

</details>

<details><summary>packages/eslint-plugin-patternfly-react/package.json</summary>

 - `@babel/eslint-parser ^7.19.1`
 - `eslint-config-airbnb ^19.0.4`
 - `eslint-config-prettier ^9.0.0`
 - `eslint-config-standard ^17.0.0`
 - `eslint-config-standard-jsx ^11.0.0`
 - `eslint-config-standard-react ^13.0.0`
 - `eslint-plugin-import ^2.13.0`
 - `eslint-plugin-jest ^27.0.0`
 - `eslint-plugin-jsx-a11y ^6.0.3`
 - `eslint-plugin-node ^11.0.0`
 - `eslint-plugin-prettier ^5.0.0`
 - `eslint-plugin-promise ^6.0.0`
 - `eslint-plugin-react ^7.7.0`
 - `eslint-plugin-react-hooks ^4.1.2`
 - `eslint-plugin-rulesdir ^0.2.0`
 - `eslint-plugin-standard ^4.0.0`
 - `eslint >=5`

</details>

<details><summary>packages/react-charts/package.json</summary>

 - `fs-extra ^11.0.0`

</details>

<details><summary>packages/react-code-editor/package.json</summary>

 - `react-dropzone 14.2.3`

</details>

<details><summary>packages/react-core/package.json</summary>

 - `react-dropzone ^14.2.3`
 - `@patternfly/patternfly 5.2.0`
 - `@rollup/plugin-commonjs ^25.0.0`
 - `@rollup/plugin-node-resolve ^15.0.2`
 - `@rollup/plugin-replace ^5.0.2`
 - `fs-extra ^11.1.1`
 - `rollup ^3.21.5`
 - `rollup-plugin-scss ^4.0.0`
 - `rollup-plugin-svg 2.0.0`
 - `rollup-plugin-terser ^7.0.2`

</details>

<details><summary>packages/react-docs/package.json</summary>

 - `@patternfly/patternfly 5.2.0`
 - `@patternfly/documentation-framework ^5.0.15`
 - `@patternfly/patternfly-a11y 4.3.1`
 - `shx ^0.3.4`

</details>

<details><summary>packages/react-drag-drop/package.json</summary>


</details>

<details><summary>packages/react-icons/package.json</summary>

 - `@patternfly/patternfly 5.2.0`
 - `fs-extra ^11.1.1`

</details>

<details><summary>packages/react-integration/demo-app-ts/package.json</summary>

 - `@types/react ^18`
 - `@types/react-dom ^18`
 - `@types/react-router ^5.1.20`
 - `@types/react-router-dom ^5.3.3`

</details>

<details><summary>packages/react-integration/package.json</summary>


</details>

<details><summary>packages/react-styles/package.json</summary>

 - `@patternfly/patternfly 5.2.0`
 - `fs-extra ^11.1.1`

</details>

<details><summary>packages/react-table/package.json</summary>


</details>

<details><summary>packages/react-tokens/package.json</summary>

 - `@patternfly/patternfly 5.2.0`
 - `fs-extra ^11.1.1`

</details>

<details><summary>packages/transformer-cjs-imports/package.json</summary>


</details>

<details><summary>packages/transformer-react-styles-esm-imports/package.json</summary>


</details>

</blockquote>
</details>

---

- [ ] <!-- manual job -->Check this box to trigger a request for Renovate to run again on this repository


user: renovate[bot]
issue_6115: state: open
title: Resolve inconsistencies when forwarding components
body: **Describe the issue. What is the expected and unexpected behavior?**

Sometimes as a user you want to be able to pass in your custom component to render instead of the default element. However the API around this varies wildly per component. For example, these are some components we use in our application that need React Router's `Link` component:

**Button**
```tsx
{/* @ts-ignore */}
<Button component={Link} to={toNewClientScope({ realm })}>
  {t("createClientScope")}
</Button>
```

**DropdownItem**
```tsx
<DropdownItem
  component={<Link to={toDashboard({ realm })}>{t("realmInfo")}</Link>}
/>
```

**BreadcrumbItem**
```tsx
<BreadcrumbItem
  render={(props) => (
    <Link {...props} to={toRealmSettings({ realm, tab: "keys" })}>
      {t("keys")}
    </Link>
  )}
/>
```

As you can see there are already three different ways of forwarding a component to render, and some of them are not able to be written in a type-safe manner.

The expected behavior here would be that this is a single and consistent API that is completely type-safe. For example, Styled Components has a `as` prop which is made [type-safe](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/styled-components/test/index.tsx#L672) by the definitions and allows the props to be forwarded and type-checked as well:

```tsx
import styled from 'styled-components'

const Button = styled.button`
  background-color: hotpink;
`

<Button component={Link} to={toNewClientScope({ realm })}>
  {t("createClientScope")}
</Button>
```

user: jonkoops
labels: breaking change :boom:: this change requires a major release and has API changes.
DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_5936: state: open
title: Draggable table should be accessible by keyboard and screen reader
body: **Describe the issue. What is the expected and unexpected behavior?**
The Composable Draggable row table should be accessible by keyboard and by screen reader. Currently it works only by mouse. I imagine that this would follow similar accessibility considerations as the [draggable datalist component](https://www.patternfly.org/v4/components/data-list/#draggable) that we implemented with this [PR](https://github.com/patternfly/patternfly-react/pull/4852). 

**Please provide the steps to reproduce. Feel free to link CodeSandbox or another tool.**
Try to use a keyboard or screen reader to interact with[ this example](https://patternfly-react-add_draggable_table.surge.sh/components/table/#composable-draggable-row-table). 

**Is this a bug or enhancement? If this issue is a bug, is this issue blocking you or is there a work-around?**
Bug
user: jessiehuff
issue_5920: state: open
title: Page: tabIndex default value (mainTabIndex=-1) which prevents keyboard scroll
body: **Describe the issue. What is the expected and unexpected behavior?**
mainTabIndex=-1 as a default value prevents keyboard scroll. tlabindex should be removed. Having a tabindex on a container essentially breaks focus and keyboard scroll for all non-focusable containers below it. eg topology details side panel.

Any contributions to the main content should not have to deal with adding their own tabindex attribute to their scroll containers.

Above notes from the pr: https://github.com/openshift/console/pull/9140#issuecomment-854134911

workaround is to set the mainTabIndex to null.

**Please provide the steps to reproduce. Feel free to link CodeSandbox or another tool.**
<!-- PatternFly-React Codesandbox template: https://codesandbox.io/s/serverless-cherry-q9t3f -->
https://github.com/openshift/console/pull/9140#issuecomment-8541349113

**Is this a bug or enhancement? If this issue is a bug, is this issue blocking you or is there a work-around?**
Bug
**What is your product and what release version are you targeting?**
OpenShift 4.9
user: jcaianirh
labels: breaking change :boom:: this change requires a major release and has API changes.
issue_5904: state: open
title: Select with checkbox input has axe violation
body: **Describe the issue. What is the expected and unexpected behavior?**
Potential accessibility issue. A recent change in @patternfly/react-core changed the way the `Select` component with checkboxes is rendered. We use [jest-axe](https://www.npmjs.com/package/jest-axe) to scan our project, and this error came up:

```
Certain ARIA roles must contain particular children (aria-required-children)

Fix any of the following:
Required ARIA child role not present: option  

You can find more information on this issue here: 
https://dequeuniversity.com/rules/axe/4.2/aria-required-children?application=axeAPI
```

**Please provide the steps to reproduce. Feel free to link CodeSandbox or another tool.**
With the [`Select` **Checkbox input** example](https://codesandbox.io/s/v0k1c) on `@patternfly/react-core` version 4.128.2, when the select is expanded, it's rendered like this:
```
<ul class="pf-c-select__menu" role="listbox" aria-label="Select Input">
  <label class="pf-c-check pf-c-select__menu-item pf-m-description">
    <input id="pf-random-id-0-Active" class="pf-c-check__input" type="checkbox" />
    <span class="pf-c-check__label">Active</span>
    <div class="pf-c-check__description">This is a description</div>
  </label>
  ...
</ul>
```

If you switch the `@patternfly/react-core` version back to 4.121.1, it used to be rendered like this:
```
<fieldset aria-label="Select Input" class="pf-c-form__fieldset">
  <label class="pf-c-check pf-c-select__menu-item pf-m-description">
    <input id="pf-random-id-0-Active" class="pf-c-check__input" type="checkbox">
    <span class="pf-c-check__label">Active</span>
    <div class="pf-c-check__description">This is a description</div>
  </label>
  ...
</fieldset>
```

I wasn't able to track down when exactly the change occurred, but it seems like it might be causing an accessibility problem.

**Is this a bug or enhancement? If this issue is a bug, is this issue blocking you or is there a work-around?**
Bug. Not a blocker but wanted to bring this to the attention of the PatternFly team.

**What is your product and what release version are you targeting?**
RHACM. No specific timeline for a fix is requested.

user: KevinFCormier
issue_5838: state: open
title: Button: remove danger variant in favor of isDanger
body: remove `danger` and `warning` variants 
remove `isDanger` prop

in favor of new prop `status: 'danger' | 'warning'`
console warning if people try to apply statuses to the improper variants:

- danger only applies to 'primary', 'link', and 'secondary' variants
   - right now, `pf-m-danger` with no other modifier class, it looks like a primary danger button
   - `pf-m-danger` + `pf-m-link|pf-m-secondary` looks like the various variant danger style
- warning only applies to 'primary' variants


user: redallen
labels: breaking change :boom:: this change requires a major release and has API changes.
Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.
issue_5397: state: open
title: Let's get stricter about (not) usage of properties that help accessibilty
body: Very often there are instructions to use `aria-label` or similar accessibility attributes as part of the component properties. My feeling is that one can very easily miss them.

See the button example: https://www.patternfly.org/v4/components/button#button

In the property section it exposes the `aria-label`, which is actually not necessary for buttons having string type children, but rather for icons buttons it is a must.

 For most of the consumers I would bet this is not clear at all, in Cockpit we have most of the icons buttons not accessible in fact, because we just were not so familiar with the accessibility rules 1 year ago. So how about going over all these accessibility related properties, and throw some warnings/errors if they are not used when they should?

CC @evwilkin @nicolethoen @tlabaj 

We should do an audit of our components (listed below) and determined whether:

- Any props should or shouldn't be required
- Any default values should be added, removed, or updated
- Any console warnings should be added, removed, or updated (e.g. warn that X prop must be passed in if Y prop isn't, or that X and Y props can't both be passed)

Components:
- [ ] About modal
- [ ] Accordion
- [ ] Action list
- [ ] Alert
- [ ] Avatar
- [ ] Backdrop
- [ ] Back to top
- [ ] Background image
- [ ] Badge
- [ ] Banner
- [ ] Brand
- [ ] Breadcrumb
- [ ] Button
- [ ] Calendar month
- [ ] Card
- [ ] Checkbox
- [ ] Chip
- [ ] Clipboard copy
- [ ] Code block
- [ ] Code editor
- [ ] Datalist
- [ ] Date picker
- [ ] Date and time picker
- [ ] Description list
- [ ] Divider
- [ ] Drag and drop
- [ ] Drawer
- [ ] Dropdown
- [ ] Dual list selector
- [ ] Empty state
- [ ] Expandable section
- [ ] File upload
- [ ] File upload - multiple
- [ ] Form
- [ ] Form control
- [ ] Form select
- [ ] Helper text
- [ ] Hint
- [ ] Icon
- [ ] Input group
- [ ] Jump links
- [ ] Label
- [ ] List
- [ ] Login page
- [ ] Masthead
- [ ] Menu
- [ ] Menu toggle
- [ ] Modal
- [ ] Nav
- [ ] Notification badge
- [ ] Notification drawer
- [ ] Number input
- [ ] Overflow menu
- [ ] Page
- [ ] Pagination
- [ ] Panel
- [ ] Popover
- [ ] Progress
- [ ] Progress stepper
- [ ] Radio
- [ ] Search input
- [ ] Select
- [ ] Sidebar
- [ ] Simple list
- [ ] Skeleton
- [ ] Skip to content
- [ ] Slider
- [ ] Spinner
- [ ] Switch
- [ ] Tabs
- [ ] Text
- [ ] Text area
- [ ] Text input
- [ ] Text input group
- [ ] Tile
- [ ] Time picker
- [ ] Timestamp
- [ ] Title
- [ ] Toggle group
- [ ] Toolbar
- [ ] Tooltip
- [ ] Tree view
- [ ] Truncate
- [ ] Wizard
user: KKoukiou
issue_5383: state: open
title: Tooltip: investigate how to improve screen reader experience and update
body: **Describe the issue. What is the expected and unexpected behavior?**
I've noticed that our tooltip examples aren't always announced in VO. The only example that has solidly worked when I've tested lately has been the Options example, and my theory behind this is the placement in the DOM. We should investigate how we can make sure that our tooltips work in a screen reader (I'd like us to ideally also test this in other screen readers as well like NVDA and JAWS). I'm wondering if we can treat it similarly to how we treat alerts and add an `aria-live` to let screen readers know where the content will be updated and make sure it's aware of these changes. 

**Please provide the steps to reproduce. Feel free to link CodeSandbox or another tool.**
Open VO and test our tooltip examples. In Chrome, the first example works along with the Options example. In Safari, only the Options example works. I'd like to make sure all implementations of tooltip work so that we can ensure our products' tooltips work in their implementations.

**Is this a bug or enhancement? If this issue is a bug, is this issue blocking you or is there a work-around?**
bug

Remaining issues in this epic:

- [ ] #3791 - Still needs to be completed. The linked issue has a few options with their own pros. Wrapping the entire Radio component in a Tooltip will result in the tooltip being centered above the entire Radio, which visually may not be the desired effect if the Radio doesn't have a lot of content, while wrapping just the radio input in a Tooltip provides a smaller area for users to trigger it.
- [ ] https://github.com/patternfly/patternfly-react/issues/9517 - MenuItem's aren't having Tooltips applied/announced correctly
- [x] https://github.com/patternfly/patternfly-react/issues/7584 - From @thatblindgeye: In testing the dropdown component again, this time both with JAWS and NVDA, I was able to get the tooltips in the Basic example to get announced in both screen readers. This may require another test from at least 2 people to confirm which behavior is more reliable. UPDATE 8/17/2023: the deprecated Dropdown still works for me with NVDA/JAWS, however the new implementation suffers the same issue as mentioned in the above issue 9517 since it's using Menu under the hood
- [ ] #7021 - This may not require completion due to the refactor that will be done for the Dual List Selector component. UPDATE 8/17/2023: This can be resolved by removing the `disabled` attribute from the controls that have it, so that instead they're only aria-disabled. The tooltip does de-render once focus is moved out of this controls group, though.

No longer applicable:
- [x] #4446 - This is less an issue with VO/Safari and more the fact that tooltips on static elements aren't reliably announced. If the basic example is updated based on https://github.com/patternfly/patternfly-react/pull/8052#discussion_r981179134, then that plus other updates made to Tooltip (adding in aria-live for the ref examples) would cover resolving this issue.


Completed issues:
- [x] #6311
- [x] #6109
- [x] #1457
- [x] #1655
- [x] #1894
- [x] #7096
- [x] https://github.com/patternfly/patternfly-org/issues/2596
- [x] https://github.com/patternfly/patternfly-react/issues/7331
user: jessiehuff
issue_5362: state: open
title: Slider:  Add integration test
body: **Describe the issue. What is the expected and unexpected behavior?**
Add more integration test to the slider
user: tlabaj
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_5131: state: open
title: Add a11y demo for Bar Chart
body: **Describe the issue. What is the expected and unexpected behavior?**
Since Victory added the support for change the role of `<svg>`, now we can first add an a11y demo to bar chart that support focus and screen reader.

**Is this a bug or enhancement? If this issue is a bug, is this issue blocking you or is there a work-around?**
Enhancement.


user: DaoDaoNoCode
issue_4912: state: open
title: Write Integration tests/demos for date and time pickers
user: nicolethoen
labels: Tech debt: improvements to code that do not affect either user or product developers’ experience.
issue_4776: state: open
title: Create demos for DataList
body: Replicate core demos for DataList here as React demos to have parity: https://staging.patternfly.org/v4/components/data-list/html-demos

Demos include

- [x] #8982
- [ ] Actionable
- [ ] Expandable
- [ ] Static bottom pagination

*Note: Please add issues as you pick up tasking
user: mcarrano
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_5879: state: open
title: Create date/time picker demo that incorporates time zones
body: Create a demo that shows how the date/time picker can be pared with a select list for picking a time zone. Time zones will be expressed as offsets from GMT and changing the timezone would result in re-calculating the date object derived from post-processing the user entered date and time value.

The default setting of time zone should be the local time zone (read from the bowser?).
user: nicolethoen
labels: DevX: enhances the consumer developer experience but does not change the experience for the end-user
issue_4281: state: open
title: Progress component accessibility enhancements
body: **Describe the issue. What is the expected and unexpected behavior?**
Currently we don't have live-region support for the progress component. When a progressbar's value is updated, I think unless the user is focused on the progress bar or re-focuses the progress bar, the new value is not necessarily announced to screen reader users (SRU). Maybe there could be a simple prop to turn it into a live region? I wouldn't think to make it a live region by default, but the option would be nice. This could help solve the case below from the usage and behavior guidelines for progressbar.

>When a process needs to be reflected to a user that is happening in the background, especially when this may take a long time

Also, the progress component isn't currently navigable from the two primary methods of navigating for screen reader users (Rotor menu and shortcut key nav), so unless they use a technique like VO cursor navigation, the screen reader user can't consume this content. It's not interactive in the sense that the user can directly interact with it, but it is in the sense that the content is dynamic and the user may wish to monitor the progress in some explicit way (such as focusing the element until progress is complete) - so for that reason, I think we should consider making it appear in the rotor menu.

**Please provide the steps to reproduce. Feel free to link CodeSandbox or another tool.**
- go to https://patternfly-react.surge.sh/documentation/react/components/progress
- turn on VO (command & F5)
- Open up the rotor, notice that the progress bar isn't in any rotor menu

**Is this a bug or enhancement? If this issue is a bug, is this issue blocking you or is there a work-around?**
I would consider this an enhancement. The progress component is accessible, but there are scenarios in which it could be made a better user experience.
user: jessiehuff
issue_4135: state: open
title: Investigation on SVG accessibility
body: **Describe the issue. What is the expected and unexpected behavior?**
On the insights dashboard where there are a lot of charts, the charts have a `<title>` which comes up when hovering over the SVG for an extended period of time. The insights team found this to be a usability issue in that the title tooltip that appears can block data in some cases.
![image (1) (1) (2)](https://user-images.githubusercontent.com/28281340/80411554-5f187180-889a-11ea-977f-95df097f493e.png)


In our charts, the aria-title prop is a pass through to the Victory library. The actual Victory property is just title, but we call it aria-title to be clear. The charts are SVGs, so Victory outputs this as a title tag within the svg itself. When you have a title tag, it is native browser behavior to have a tooltip that appears when the mouse is held over a spot on the SVG for an extended period of time. This tooltip appears wherever the mouse is held on the SVG. Taking off the title tag could have potentially negative accessibility side effects.

When researching, I found this article that explains all the different combinations that can be done with SVGs and how they work across different screen readers which provides excellent guidance with the accessibility: https://www.deque.com/blog/creating-accessible-svgs/
Based on the research, it appears that the most recommended combination is `<svg> + role="img" + <title> + <desc> + aria-labelledby="[ID]"` as it was the most reliable choice for the different browser and screen readers that were tested. As the above article explains, taking off the title is not preferred for most use cases as it can cause the SVG to be significantly less accessible. You can remove the title element and add an aria-label like in Pattern 3 in this research, however it will cause the SVG to be read as an image so the user will be unable to interact as easily with the chart by screen reader.

We should investigate if there are improvements that could be made to our charts/SVG accessibility and see if there are better solutions to the title tooltip concerns.


**Please provide the steps to reproduce. Feel free to link CodeSandbox or another tool.**
<!-- PatternFly-React Codesandbox template: https://codesandbox.io/s/serverless-cherry-q9t3f -->
If you go to our pie chart example and hover over any section of the chart, you can see the title tooltip appear. This appears to be the concern that Insights is having: https://www.patternfly.org/v4/documentation/react/charts/chartpie/basic-with-right-aligned-legend


**Is this a bug or enhancement? If this issue is a bug, is this issue blocking you or is there a work-around?**
Enhancement to our charts accessibility.
Work around - if you see this as a significant usability issue for visual users, you can take off the title as long as it's replaced with something else like a proper aria-desc to ensure the user is getting the information. You could use an aria-label, but you have to be aware of the fact that it will make the svg be read as an image and be less accessible. You would need to relay the information inside the chart in a different way to screen reader users. The above article explains all of the different combinations that you could try and the different results you will have given the pattern you choose.

user: jessiehuff
issue_3953: state: open
title: Add keyboard interaction accessibility tests
body: **Describe the issue. What is the expected and unexpected behavior?**
We should write cypress keyboard interaction accessibility tests for our components in order to prevent future regressions, focus should be given to the most popular components: 
- [x] Button
- [ ] Modal
- [ ] Card
- [ ] Form
- [ ] Alert
- [ ] Empty State
- [ ] Tooltip 

(All dropdown related components captured in a separate issue: #3108)

**Is this a bug or enhancement? If this issue is a bug, is this issue blocking you or is there a work-around?**
This would be an enhancement to cut down on manual testing time. 


user: jessiehuff
issue_3791: state: open
title: Tooltips for disabled radio
body: For a tooltip to be accessible for keyboard-only users, the element with the tooltip needs to be able to receive keyboard focus. Elements like `<button>` that support the `disabled` attribute cannot receive keyboard focus. 

To continue to render these elements as disabled but enable keyboard focus, the following changes are needed:
- Remove `disabled`
- Add `aria-disabled="true"`
- Make sure the `pf-m-disabled` class or similar is included on the element to apply the disabled styling.
- If the element is a link, remove `tabindex="-1"`

We should update all interactive elements to include a prop that allows the consumer to make the element disabled but focusable so the element can be used with the Tooltip component. This prop should apply the appropriate attributes and classes for the given element.

Unless someone has a better suggestion, the prop could be named `isDisabledFocusable` (totally open to suggestions on this one)
user: jessiehuff
labels: Feature: end user feature that requires design to define this, i.e. changes or augments the user experience.