Skip to content

Conversation

@mindspank
Copy link
Contributor

Makes sure we handle spaces in searches for measure and dims

Checklist:

  • Covered by tests
  • Ran it and it works as intended
  • Reviewed the diff before requesting a review
  • Checked for unhandled edge cases
  • Linked the issues it closes
  • Checked if the docs need to be updated. If so, create a separate Linear DOCS issue
  • Intend to cherry-pick into the release branch
  • I'm proud of this work!
Comment on lines +39 to +40
.map((id) => {
const itemData = allItemsMap.get(id);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This avoids a redundant map lookup:

.map(([id, itemData]) => ({
    id: id!,
    displayName: itemData?.displayName ?? id!,
  }));
Comment on lines 50 to 51
.map(([id]) => {
const itemData = allItemsMap.get(id!);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

@mindspank mindspank merged commit ef9268a into main Dec 13, 2025
10 checks passed
@mindspank mindspank deleted the fix/whitespacesearch branch December 13, 2025 12:58
mindspank added a commit that referenced this pull request Dec 13, 2025
* fix: spaces in measure/dim search

* fix loop

* revert
k-anshul pushed a commit that referenced this pull request Dec 18, 2025
* fix: spaces in measure/dim search

* fix loop

* revert
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants