-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Audit components to remove getSlotted
util instances
#6059
Comments
This one would be nice to get onto a milestone sometime in the next year. |
* origin/main: chore: release next chore: add `directory` to package.json `repository` property (#7510) fix(action-bar): restore "bottom-actions" slot functionality. (#7535) refactor(action-bar, action-pad, action-group): Remove usage of getSlotted utility (#7464) build(deps): update dependency lerna to v7.1.5 (#7502) build(deps): update dependency @esri/calcite-ui-icons to v3.23.7 (#7522) refactor(shell-panel): Remove usage of getSlotted utility. #6059 (#7465) build(deps): update dependency eslint-plugin-unicorn to v46.0.1 (#7501) build(deps): replace dependency rollup-plugin-node-resolve with @rollup/plugin-node-resolve 6.0.0 (#7481) test: skip unstable tests (#7524) build(deps): update dependency lint-staged to v13.2.3 (#7523) build(deps): update dependency @types/estree to v1.0.1 (#7483) build(deps): update dependency eslint-plugin-react to v7.33.1 (#7500) build(deps): update dependency eslint-plugin-jsdoc to v46.4.6 (#7499) build(deps): update dependency @types/node to v20.4.10 (#7484) chore: release next chore: release main (#7485)
See my comment on 10152. Hub is observing certain slotted contents not working in |
**Related Issue:** #6059 ## Summary - remove use of `getSlotted` utility - replace with `slotchange` event and `@State` variables to update the display of elements. - existing tests should suffice
**Related Issue:** #6059 ## Summary - remove use of `getSlotted` utility - replace with `slotchange` event and `@State` variables to update the display of elements. - existing tests should suffice
**Related Issue:** #6059 ## Summary - remove use of `getSlotted` utility - replace with `slotchange` event and `@State` variables to update the display of elements. - existing tests should suffice
**Related Issue:** #6059 ## Summary - remove use of `getSlotted` utility - replace with `slotchange` event and `@State` variables to update the display of elements. - existing tests should suffice
@driskull's been crushing it with this audit! Some of the associated PRs are fixes, so we might need to adjust this issue to accommodate for testing and verification. cc @geospatialem @DitwanP |
) **Related Issue:** #6059 ## Summary - remove use of `getSlotted` utility - replace with `slotchange` event - existing tests should suffice
Should we update |
**Related Issue:** #6059 ## Summary - remove use of `getSlotted` utility - replace with `slotchange` event and `@State` variables to update the display of elements. - existing tests should suffice
**Related Issue:** #6059 ## Summary - remove use of `getSlotted` utility - replace with `slotchange` event and `@State` variables to update the display of elements. - existing tests should suffice
**Related Issue:** #6059 ## Summary - remove use of `getSlotted` utility - replace with `slotchange` event and `@State` variables to update the display of elements. - existing tests should suffice
Installed and assigned for verification. |
🍠✨ Verified. The e2e and screenshot tests does indeed provide good coverage for this! 💪 |
Agreed. We can also keep an eye out for anything our testing may have missed. For context, the fix-side on the related PRs addresses the point from this PR:
|
**Related Issue:** #6059 ## Summary - remove `getSlotted()` util and tests - remove `ConditionalSlotComponent` utility file. - remove `getElementProp()` util. Unused. - depends on removal of `pick-list` and `value-list` components.
Description
Many components use
getSlotted
and will need to be refactored in favor of a new pattern.Proposed Advantages
The
getSlotted
util is no longer a recommended pattern -onSlotChange
is preferred.Which Component
Note: prioritize
card
effort in the initial stages first, if at all possible -- related issue: #10152accordion-item
fix(accordion-item): fix rendering tied to named-slot content #10447action-bar
action-group
action-pad
alert
refactor(alert): simplify setFocus method #10448block
fix(block): fix rendering tied to named-slot content #10449card
❗ - prioritize in October 2024combobox-item
fix(combobox-item): fix rendering tied to named-slot content #10450inline-editable
fix(inline-editable): fix rendering tied to default slot content #10456input
fix(input, input-number, input-text): should not set slotted actions to be disabled #10458input-number
fix(input, input-number, input-text): should not set slotted actions to be disabled #10458input-text
fix(input, input-number, input-text): should not set slotted actions to be disabled #10458(deprecated) fix(modal): fix rendering tied to named-slot content #10469modal
notice
fix(notice): fix rendering tied to named-slot content #10453(deprecated)pick-list-group
(deprecated)pick-list-item
shell
shell-center-row
fix(shell-center-row): fix rendering tied to named-slot content #10451shell-panel
table
tile
tile-group
(deprecated) fix(tip): fix rendering tied to named-slot content #10470tip
tree-item
fix(tree, tree-item): fix rendering tied to named-slot content #10462(deprecated)value-list-item
Relevant Info
cc @driskull
The text was updated successfully, but these errors were encountered: