Closed geospatialem closed 1 year ago
Before we can tackle this, we should discuss whether we should be using the SortableList component internally here or getting rid of that component.
Before we can tackle this, we should discuss whether we should be using the SortableList component internally here or getting rid of that component.
Good idea - added to the upcoming engineering discussion to discuss options.
We need a whole sorting strategy before we can tackle this. The strategy should cover...
Adding a tag to this issue to Hub components and cc @vivzhang in regards to the issue description above:
May also include a refactor of the sortable utility, which some teams use for their own use and should be consulted if a breaking change is necessary.
Adding two pieces of feedback we got about Value List for consideration here w/r/t keyboard usage from this closed issue: https://github.com/Esri/calcite-components/issues/4231
Following up from Teams chat - some improvements to the value list while in drag-enabled mode to make using with a keyboard a bit easier:
Add support for esc to exit that mode (currently only hitting spacebar again exits the mode) Add support for home / end to quickly move an item to either extent (and preventDefault so the page doesn't scroll up / down)
Currently, in ArcGIS Urban, we have several use cases of custom lists/accordions that seem to match the List/Block/Accordion component functionality. In several cases, it's a bit difficult to choose a proper Calcite component. I would appreciate your suggestions or perhaps, our cases can turn out into future List component enhancements.
Component:
Component:
Component:
Component:
@geospatialem @jcfranco we may need to make this one a breaking change.
I'm running into trouble with sorting of children because we slot a <calcite-list-item>
inside of another <calcite-list-item>
like so:
<calcite-list>
<calcite-list-item>
<calcite-list-item></ calcite-list-item>
</calcite-list-item>
</calcite-list>
In order to fix this, we may need to require the following:
<calcite-list>
<calcite-list-item>
<calcite-list>
<calcite-list-item></ calcite-list-item>
</calcite-list>
</calcite-list-item>
</calcite-list>
Let me know if you'd like to meet to discuss this. If we do this breaking change, this milestone may need to change.
@driskull Thanks for the heads up on a potential breaking change, lets connect sometime next week. I'll set a reminder for us to chat on next steps.
Documentation update to follow the change is needed to showcase what devs will need to achieve sorting, which differs from the current workflow.
Installed and assigned for verification.
Verified with https://codepen.io/geospatialem/pen/bGQzavG in 1.5.0-next.33
. Opened #7426 for finalizing AT support.
Description
Add full parity to the
list
component, which is provided in thevalue-list
andpick-list
components.May also include a refactor of the
sortable
utility, which some teams use for their own use and should be consulted if a breaking change is necessary.Acceptance Criteria
list-item
sRelevant Info
Part of the https://github.com/Esri/calcite-components/issues/6430 epic
Which Component
Example Use Case
Depicted with
value-list
andvalue-list-item
: https://codepen.io/geospatialem/pen/abjxWwLEsri team
Calcite (dev)