Closed cooper-joe closed 4 years ago
@edoardo This is the change you are waiting on for Data Visualizer YoY controls.
@varl @ismay should this go into ui-core
or ui
?
Project | ui-core |
Status | Passed |
Commit | 65453b87a4 |
Started | Apr 15, 2020 9:31 AM |
Ended | Apr 15, 2020 9:38 AM |
Duration | 07:16 💡 |
OS | Linux Ubuntu Linux - 18.04 |
Browser | Electron 78 |
View run in Cypress Dashboard ➡️
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard
I'd personally say ui@alpha, the NoticeBox is also there for example. Otherwise we have changes in ui-core that we'd have to pull into ui. But I don't know what @varl prefers. Plus it depends on the timeline for this change (it will take a bit until the ui stable release), ui-core could be released r.n.
I'd say that this is a fix:
, as a fix doesn't have to be a straight up bug fix, it can be a design fix or something else that fixes something without introducing a new feature.
As for where it goes, merging from ui-core to ui is relatively straight forward, so this can go here as it is being waited on.
I'd say that this is a
fix:
, as a fix doesn't have to be a straight up bug fix, it can be a design fix or something else that fixes something without introducing a new feature.
Thanks for the clarification @varl, that makes sense to me now. I've changed the commit message.
:tada: This PR is included in version 4.17.1 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
This PR changes the
Chip
type used in aMultiSelect
. It adds adense
prop to theChip
.Note: is this the correct conventional commit message type? It's not a
fix:
because this was not a bug, but is there something beforefeat:
, more like...adjustment:
? 😉