-
Notifications
You must be signed in to change notification settings - Fork 4
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
Airplane icon added (angled) #497
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
--- | ||
'@cypress-design/react-icon': minor | ||
'@cypress-design/vue-icon': minor | ||
'@cypress-design/icon-registry': minor | ||
--- | ||
|
||
Share icon added |
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. @emilmilanov Instead of just "share" as the name, would it make sense to call them "share-airplane" or something like that in case we ever add different icons for "share"? 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 think I agree on that. I do think that the icons should probably just reflect the name of whatever it is that has been illustrated instead of a semantic name. (i.e. airplane, airplane-angled, etc) |
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.
@emilmilanov I believe that the icon updates were considered as
patch
updates, instead ofminor
typically. We should probably continue to follow that pattern. Everything else looks good though.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.
In looking at older PRs that introduce new icons, I saw both
minor
andpatch
used.From a semantic versioning definition, I think this type of change would align with
minor
: "when you add functionality in a backward compatible manner"But I think you could argue either way.
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 used
yarn changeset
to create this part of the code; it doesn't offer apatch
option, only major or minor. I can override this to patch if we agree on it. When I added icons to the DS before, I always usedminor
.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.
@warrensplayer I'll let you make the final call on that. I'd rather just make sure we know which pattern to use and to stick with that. If you've got strong feelings on the matter, we'll just follow your lead.
That said, I kind of just guessed that bart was using
patch
updates more often as to not run out of minor numbers. I don't know how many numbers are available before a major version is required. Maybe it's endless?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.
@ryanjwilke There is no limit to the numbers.
@emilmilanov I did go back and look a little bit harder and the CHANGELOG.md files and it does seem like most of the changes that add icons use
patch
. So I guess update your changeset file to usepatch
as well for all three packages.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.
Changeset is updated from
minor
topatch
. I also renamed icons to object-airplane-angled...