-
Notifications
You must be signed in to change notification settings - Fork 48
Add orcidlinks, orcidlinkm, orcidlinkl #5
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
base: master
Are you sure you want to change the base?
Conversation
jonas-schulze
commented
Dec 14, 2022
- small: current/old size
- medium: matches looks of stackoverflow post
- large: should match large variant from ORCID guidelines (preview.png)
Where should I document these new variants? Shall I refactor the variable names in favor of e.g. I just noted that I created the commit on my master. If you prefer a PR from a different/feature branch, I'm happy to open a new PR (unless it is possible to change the base branch of a PR). |
094f367
to
6e3a680
Compare
* small: current/old size * medium: matches looks of stackoverflow post * large: should match large variant from ORCID guidelines (preview.png)
6e3a680
to
9287735
Compare
Hi @jonas-schulze, this looks like it could be useful! But for backwards compatibility, the previous command |
I haven't used |
Sorry that I wasn't paying close enough attention before, I missed that you created a new internal command Can you comment on why both Also, do you have any thoughts on how to minimize the code duplication between |
No rush, we can talk about this after your vacation, or next year even. (A brief heads-up would be nice, though.) 🙂
I have already thought about that, and came to no ideal solution. |
`curX*` becomes `Target*` as it isn't related to a capital X anymore. `*height` becomes `*Size` as it contains height and depth of a glyph.
Hi @duetosymmetry, happy new year! I hope you've had a nice vacation. I've just returned from vacation myself. ⛷️ |
bump 🙂 |
1 similar comment
bump 🙂 |