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

Add Axis Line Stroke Width #160

Merged
merged 1 commit into from
May 14, 2024
Merged

Conversation

mark-fitzgerald
Copy link
Collaborator

The current stroke width for the axis lines defaults to 1px. To aid with design considerations, there are times when the desired thickness is greater, like 2px for instance. Adding a CSS variable for this property enables the consumer to indicate a different thickness to match their designs.

Copy link

vercel bot commented May 13, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
mafs-6swq ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 13, 2024 9:41pm

Copy link
Owner

@stevenpetryk stevenpetryk left a comment

Choose a reason for hiding this comment

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

Reasonable! The publish failures are an auth token thing—will fix.

@stevenpetryk stevenpetryk merged commit 62aa665 into main May 14, 2024
7 of 8 checks passed
@stevenpetryk stevenpetryk deleted the axis-line-stroke-width-customization branch May 14, 2024 23:24
benchristel added a commit to Khan/perseus that referenced this pull request May 22, 2024
0.18.6 demands node version 20.11 or higher, which we don't yet have
everywhere (e.g. webapp's Jenkins server runs 20.5). By downgrading,
we lose a couple features we submitted:

- stevenpetryk/mafs#159
- stevenpetryk/mafs#160

However, I think temporarily sacrificing these features is an okay
tradeoff, because otherwise we cannot release Perseus into webapp.

Longer term, we may be able to convince Steven (the Mafs maintainer) to
relax the node version constraint to something like `>= 20`. I don't
think Mafs actually needs 20.11 specifically.

Issue: none

Test plan:

- Release a new version of Perseus
- Upgrade Perseus in webapp
- All tests should pass on webapp CI
benchristel added a commit to Khan/perseus that referenced this pull request May 23, 2024
## Summary:
0.18.6 demands node version 20.11 or higher, which we don't yet have
everywhere (e.g. webapp's Jenkins server runs 20.5). By downgrading,
we lose a couple features we submitted:

- stevenpetryk/mafs#159
- stevenpetryk/mafs#160

However, I think temporarily sacrificing these features is an okay
tradeoff, because otherwise we cannot release Perseus into webapp.

Longer term, we may be able to convince Steven (the Mafs maintainer) to
relax the node version constraint to something like `>= 20`. I don't
think Mafs actually needs 20.11 specifically.

Issue: none

Test plan:

- Release a new version of Perseus
- Upgrade Perseus in webapp
- All tests should pass on webapp CI

Author: benchristel

Reviewers: nishasy, #perseus, jeremywiebe, mark-fitzgerald

Required Reviewers:

Approved By: nishasy

Checks: ✅ codecov/project, ✅ codecov/patch, ✅ Upload Coverage (ubuntu-latest, 20.x), ✅ Publish npm snapshot (ubuntu-latest, 20.x), ✅ Lint, Typecheck, Format, and Test (ubuntu-latest, 20.x), ✅ Check builds for changes in size (ubuntu-latest, 20.x), ✅ Cypress (ubuntu-latest, 20.x), ✅ Jest Coverage (ubuntu-latest, 20.x), ✅ Publish Storybook to Chromatic (ubuntu-latest, 20.x), ✅ Check for .changeset entries for all changed files (ubuntu-latest, 20.x), ✅ gerald

Pull Request URL: #1300
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants