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

chore(sort-handle): add messages #10474

Merged
merged 12 commits into from
Oct 7, 2024
Merged

Conversation

driskull
Copy link
Member

@driskull driskull commented Oct 2, 2024

Related Issue: #7537

Summary

  • add messages for translation

@driskull driskull marked this pull request as ready for review October 2, 2024 18:45
@driskull driskull requested a review from anveshmekala October 2, 2024 18:46
@github-actions github-actions bot added the chore Issues with changes that don't modify src or test files. label Oct 2, 2024
Copy link
Member

@jcfranco jcfranco left a comment

Choose a reason for hiding this comment

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

✨🧶✨

@driskull driskull changed the title chore(sort-dropdown): add messages chore(sort-handle): add messages Oct 2, 2024
@driskull driskull added the skip visual snapshots Pull requests that do not need visual regression testing. label Oct 2, 2024
@driskull driskull requested a review from geospatialem October 2, 2024 19:55
@driskull
Copy link
Member Author

driskull commented Oct 2, 2024

@geospatialem could you review the strings?

@driskull
Copy link
Member Author

driskull commented Oct 2, 2024

@geospatialem instead of using direction like up/down/top/bottom, would it be better to use non directional terms?

  • forward/backward/start/end
  • ahead/behind/start/end
  • next/previous/first/last

Then again, maybe its ok to leave as top/bottom/up/down since I don't think we'll do horizontal sorting.

Example UI for context

image

If you want to test it out a bit, you can use this PR: #10480

Copy link
Member

@geospatialem geospatialem left a comment

Choose a reason for hiding this comment

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

LGTM! 💪🏻

@geospatialem instead of using direction like up/down/top/bottom, would it be better to use non directional terms?

forward/backward/start/end
ahead/behind/start/end
next/previous/first/last

@driskull Think its okay to leave as-is, while we could have more coverage and consistency, this seems a bit more confusing to list "Move to start" / "Move to end". If we do move to horizontal sorting we could consider alternative approaches in the future.

@driskull driskull merged commit 7e8a8bc into dev Oct 7, 2024
11 checks passed
@driskull driskull deleted the dris0000/sort-dropdown-messages branch October 7, 2024 18:10
@github-actions github-actions bot added this to the 2.13.1 patch milestone Oct 7, 2024
benelan added a commit that referenced this pull request Oct 7, 2024
* origin/dev: (230 commits)
  chore: release next
  chore(sort-handle): add messages (#10474)
  feat(accordion-item): stretch slotted actions to fill its height (#9250)
  chore: release next
  feat(dialog, modal, popover, input-date-picker,  input-time-picker, sheet): support stacked component sequential closing with escape (#9231)
  chore: remove commented-out code (#10478)
  chore: add cssrem VSCode extension recommendation (#10300)
  docs(accordion-item): fix deprecation tag (#10479)
  chore: release next
  feat(stepper-item): update component's active state background color. (#10475)
  refactor: use `requestAnimationFrame` to replace `readTask` (#10432)
  chore: release next
  fix(tip): fix rendering tied to named-slot content (#10470)
  ci: compile estimate totals per milestone (#10442)
  chore: release next
  fix(modal): fix rendering tied to named-slot content (#10469)
  chore: release next
  fix(shell-center-row): fix rendering tied to named-slot content (#10451)
  fix(inline-editable): fix rendering tied to default slot content (#10456)
  fix(input, input-number, input-text): should not set slotted actions to be disabled (#10458)
  ...
@geospatialem geospatialem removed this from the 2.13.1 patch milestone Oct 7, 2024
benelan pushed a commit that referenced this pull request Feb 8, 2025
**Related Issue:** #7537

## Summary

- add messages for translation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Issues with changes that don't modify src or test files. skip visual snapshots Pull requests that do not need visual regression testing.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants