-
-
Notifications
You must be signed in to change notification settings - Fork 592
Alphabetize the Product Drive Participant drop-downs (#5593) #5656
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
Open
pcbeingused333
wants to merge
1
commit into
rubyforgood:main
Choose a base branch
from
pcbeingused333:5593-alphabetize-participant-dropdowns
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -30,7 +30,27 @@ class ProductDriveParticipant < ApplicationRecord | |
| validates :business_name, presence: { message: "Must provide a name or a business name" }, if: proc { |pdp| pdp.contact_name.blank? } | ||
| validates :comment, length: { maximum: 500 } | ||
|
|
||
| scope :alphabetized, -> { order(:contact_name) } | ||
| # Orders on the name the drop-downs actually show - `display_name`, which is | ||
| # `business_name` falling back to `contact_name` - rather than on the database | ||
| # collation, which is not the same everywhere: a `C.UTF-8` cluster puts every | ||
| # capitalised name before every lowercase one and the `en_US.utf8` image CI | ||
| # runs does not. Runs of digits are zero padded so that they compare by value | ||
| # and "Store 9" comes before "Store 10". | ||
| # | ||
| # Written as a literal because the schema is maintained as `schema.rb`, which | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I feel like adding a Postgres function with something like this would be more generally useful. We know we want to apply this ordering to other places. You can look at something like fx to handle it. |
||
| # carries neither a Postgres function nor an ICU collation - both would | ||
| # disappear on `db:schema:load`. | ||
| DISPLAY_NAME_ORDER = Arel.sql(<<~SQL.squish) | ||
| (SELECT string_agg( | ||
| CASE WHEN chunk[1] ~ '^[0-9]' THEN lpad(chunk[1], 20, '0') ELSE chunk[1] END, | ||
| '' ORDER BY idx) | ||
| FROM regexp_matches( | ||
| lower(coalesce(NULLIF(business_name, ''), contact_name, '')), | ||
| '[0-9]+|[^0-9]+', 'g') | ||
| WITH ORDINALITY AS chunks(chunk, idx)) | ||
| SQL | ||
|
|
||
| scope :alphabetized, -> { order(DISPLAY_NAME_ORDER) } | ||
| scope :by_business_name, ->(business_name) { where("business_name ILIKE ?", "%#{business_name}%") } | ||
| scope :by_contact_name, ->(contact_name) { where("contact_name ILIKE ?", "%#{contact_name}%") } | ||
| scope :with_volumes, -> { | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure that was part of the original requirements (only if the string starts with a number, not if there's a number in the middle of the string). @ruestitch thoughts? That might simplify this function.