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

Fix multi-schema data selector header styling #40101

Merged
merged 2 commits into from Mar 15, 2024
Merged

Fix multi-schema data selector header styling #40101

merged 2 commits into from Mar 15, 2024

Conversation

nemanjaglumac
Copy link
Member

@nemanjaglumac nemanjaglumac commented Mar 13, 2024

  • Makes spacing equal on both sides of the divider
  • Changes the divider from the hyphen to the forward slash

Before

image

After

image

Fixes #39999

- Makes spacing equal on both sides of the divider
- Changes the divider from the hyphen to the forward slash
@nemanjaglumac nemanjaglumac added the backport Automatically create PR on current release branch on merge label Mar 13, 2024
@nemanjaglumac nemanjaglumac requested a review from a team March 13, 2024 19:16
Copy link

replay-io bot commented Mar 13, 2024

Status In Progress ↗︎ 55 / 56
Commit 320d033
Results
⚠️ 8 Flaky
2354 Passed

Copy link
Contributor

@mazameli mazameli left a comment

Choose a reason for hiding this comment

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

Nit/question: in your screenshots the words "Multi-schema" and "Schema two" look slightly like different colors. Are my eyes deceiving me?

But as for the actual issue being addressed in this PR: I love your attention to detail, and I'm cool with the change here.

@nemanjaglumac
Copy link
Member Author

Are my eyes deceiving me?

They are not.
Chrome vs Firefox screenshots :)

@nemanjaglumac nemanjaglumac merged commit 35cf89a into master Mar 15, 2024
107 checks passed
@nemanjaglumac nemanjaglumac deleted the fix-39999 branch March 15, 2024 09:16
Copy link

@nemanjaglumac Did you forget to add a milestone to the issue for this PR? When and where should I add a milestone?

github-actions bot pushed a commit that referenced this pull request Mar 15, 2024
* Fix multi-schema data selector header styling

- Makes spacing equal on both sides of the divider
- Changes the divider from the hyphen to the forward slash

* Change the breadcrumb divider in the Table Metadata section
metabase-bot bot added a commit that referenced this pull request Mar 15, 2024
* Fix multi-schema data selector header styling

- Makes spacing equal on both sides of the divider
- Changes the divider from the hyphen to the forward slash

* Change the breadcrumb divider in the Table Metadata section

Co-authored-by: Nemanja Glumac <31325167+nemanjaglumac@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Automatically create PR on current release branch on merge .Team/QueryingComponents
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inconsistent spacing around table and schema divider
2 participants