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

Record Selector styling #2185

Merged
merged 7 commits into from
Jan 11, 2023
Merged

Record Selector styling #2185

merged 7 commits into from
Jan 11, 2023

Conversation

seancolsen
Copy link
Contributor

@seancolsen seancolsen commented Jan 3, 2023

Fixes #2104

Before this PR

image

Figma design

image

After this PR

image

Notable differences vs Figma

  • I used a thicker outline to indicate focus of the current input.
  • I adjusted the yellow color of the match highlight slightly to give it more contrast.

Checklist

  • My pull request has a descriptive title (not a vague title like Update index.md).
  • My pull request targets the master branch of the repository
  • My commit messages follow best practices.
  • My code follows the established code style of the repository.
  • I added tests for the changes I made (if applicable).
  • I added or updated documentation (if applicable).
  • I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@seancolsen seancolsen added the pr-status: review A PR awaiting review label Jan 3, 2023
@seancolsen seancolsen assigned pavish and rajatvijay and unassigned pavish Jan 3, 2023
@seancolsen
Copy link
Contributor Author

(Re-assigning review to Rajat because I see that Pavish currently has several other PRs to review.)

@codecov-commenter

This comment was marked as off-topic.

@pavish
Copy link
Member

pavish commented Jan 3, 2023

@seancolsen The consistency fixes PR contains some styling changes which affect the record selector. Do you think you could base your PR on top of it, and resolve conflicts? This would be much faster than the other way around. Also, I expect the consistency fix PR to be merged tomorrow.

@seancolsen seancolsen changed the base branch from master to consistency-fixes January 3, 2023 19:56
@seancolsen
Copy link
Contributor Author

base your PR on top of it, and resolve conflicts

Thanks for pointing that out, @pavish. Done.

@seancolsen seancolsen mentioned this pull request Jan 3, 2023
Copy link
Contributor

@rajatvijay rajatvijay left a comment

Choose a reason for hiding this comment

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

@seancolsen I saw 2 weird things happening here:

  1. Layout shift when searching inside the record selector: https://www.loom.com/share/29ca246255cd4ba298fdf9308bca0529
  2. In the below screenshot the Acquisition Date has no matches but the results are still shown because of the id and Acquisition price match. It might make sense but it looked a bit weird to me at first look.

Screenshot 2023-01-05 at 1 02 46 PM

@rajatvijay rajatvijay added pr-status: revision A PR awaiting follow-up work from its author after review and removed pr-status: review A PR awaiting review labels Jan 5, 2023
@rajatvijay rajatvijay assigned seancolsen and unassigned rajatvijay Jan 5, 2023
Base automatically changed from consistency-fixes to master January 5, 2023 19:19
@seancolsen
Copy link
Contributor Author

seancolsen commented Jan 5, 2023

@rajatvijay This is ready for re-review now.

  • Re: (1) Layout shift -- this is tracked in Keep records in store while fetching #1893

  • Re: (2) Matches looking weird:

    • I had opened Highlight matching cells in temporal cell types within the Record Selector #1889 a while back to track this issue specifically for temporal types. This partially addresses your comment because you're experiencing unexpected behavior with the "Acquisition Date" column. Today I just updated the description of that ticket, providing a better screenshot an some notes on implementation.

    • I thought I had also addressed this same problem for other data types (e.g. Number, Money), but seeing your screenshot above raised my eyebrows, surprising me that matches within the "id" and "Acquisition Price" columns were not appropriately highlighted.

      I just pushed 361537a to address this. My fix adds match highlighting to Number, Money, Boolean, and Linked Record cell types. You can see the results below.

      image

      image

      I hope the yellow makes the behavior clear enough to the user.

    • The lack of highlighting in temporal column types is apparent in my second screenshot above by the fact that the first cell in the "date" column is not highlighted. I'm punting this work until later because the fix requires more work since the values can be formatted in different ways but still be equal. We can continue to discuss the details and prioritization of that work within that ticket.

@seancolsen seancolsen assigned rajatvijay and unassigned seancolsen Jan 5, 2023
@seancolsen seancolsen added pr-status: review A PR awaiting review and removed pr-status: revision A PR awaiting follow-up work from its author after review labels Jan 5, 2023
@rajatvijay
Copy link
Contributor

@seancolsen LGTM 🚀

@rajatvijay rajatvijay merged commit 9409e65 into master Jan 11, 2023
@rajatvijay rajatvijay deleted the record_selector_styling branch January 11, 2023 19:14
@kgodey
Copy link
Contributor

kgodey commented Jan 11, 2023

@rajatvijay I had to dismiss your review to get this merged, please remember to use the "approve" functionality. Otherwise, auto-merge won't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr-status: review A PR awaiting review
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

Implement record selector styling updates
5 participants