Skip to content
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

Common resource to store debounce consts #5371

Closed
driskull opened this issue Sep 21, 2022 · 2 comments
Closed

Common resource to store debounce consts #5371

driskull opened this issue Sep 21, 2022 · 2 comments
Assignees
Labels
4 - verified Issues that have been released and confirmed resolved. estimate - 2 Small fix or update, may require updates to tests. p - medium Issue is non core or affecting less that 60% of people using the library refactor Issues tied to code that needs to be significantly reworked.

Comments

@driskull
Copy link
Member

driskull commented Sep 21, 2022

Background

Sidebar: maybe we need a common resource to store these types of consts. I think debouncing would follow the same delay.

#4527 (comment)

It would be nice if we had a location where we all shared common debounce timeouts for usage throughout components.

Desired Outcome

A utility resource to store debounce timeouts. Potentially similar to the storage of z-index values.

@driskull driskull added research Issues that require more in-depth research or multiple team members to resolve or make decision. 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. labels Sep 21, 2022
@geospatialem geospatialem added refactor Issues tied to code that needs to be significantly reworked. p - medium Issue is non core or affecting less that 60% of people using the library estimate - 2 Small fix or update, may require updates to tests. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. and removed needs triage Planning workflow - pending design/dev review. research Issues that require more in-depth research or multiple team members to resolve or make decision. labels Dec 18, 2023
@geospatialem geospatialem added this to the 2024-07-30 - Jul Release milestone Jan 10, 2024
@geospatialem geospatialem removed the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Jan 10, 2024
@Elijbet Elijbet self-assigned this Jun 27, 2024
@Elijbet Elijbet added 2 - in development Issues that are actively being worked on. and removed 0 - new New issues that need assignment. labels Jul 22, 2024
Elijbet added a commit that referenced this issue Jul 27, 2024
**Related Issue:** #5371

## Summary
Refactor: create a common resource to store debounce consts for
`action-bar`, `combobox`, `filter`, `list`, `floating-ui`.
@Elijbet Elijbet added 3 - installed Issues that have been merged to master branch and are ready for final confirmation. and removed 2 - in development Issues that are actively being worked on. labels Jul 27, 2024
Copy link
Contributor

Installed and assigned for verification.

@github-actions github-actions bot assigned geospatialem and DitwanP and unassigned Elijbet Jul 27, 2024
@DitwanP
Copy link
Contributor

DitwanP commented Jul 29, 2024

🍡 Verified

@DitwanP DitwanP closed this as completed Jul 29, 2024
@DitwanP DitwanP added 4 - verified Issues that have been released and confirmed resolved. and removed 3 - installed Issues that have been merged to master branch and are ready for final confirmation. labels Jul 29, 2024
calcite-admin pushed a commit that referenced this issue Jul 30, 2024
**Related Issue:** #5371

## Summary
Refactor: create a common resource to store debounce consts for
`action-bar`, `combobox`, `filter`, `list`, `floating-ui`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4 - verified Issues that have been released and confirmed resolved. estimate - 2 Small fix or update, may require updates to tests. p - medium Issue is non core or affecting less that 60% of people using the library refactor Issues tied to code that needs to be significantly reworked.
Projects
None yet
Development

No branches or pull requests

5 participants