-
Notifications
You must be signed in to change notification settings - Fork 333
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 anchor select field component #2813
Fix anchor select field component #2813
Conversation
This should have been done when we upgraded react-select. My bad.
@@ -95,6 +95,7 @@ class AnchorSelectorField extends SilverStripeComponent { | |||
* @param {String} value | |||
*/ | |||
handleChange(value) { | |||
console.log(value); |
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.
console.log(value); |
Oops I need to remove this
Marking this as DRAFT as it requires silverstripe/webpack-config#55 to be merged, tagged, and published in npm before I can add the emotion cache component. |
The changes to |
This ensures we can override the react-select CSS if we need to.
db48c50
to
ef4122d
Compare
Note that this PR now requires silverstripe/silverstripe-admin#1432 to be merged before it will go "green" (behat will still fail, but the tests that this PR specifically is targetting should pass) |
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.
LGTM
This should have been done when we upgraded react-select. My bad. The
Creatable
component is replaced withCreatableSelect
and along with changes to that component's props, the selectors have also changed.Fixes part of https://github.com/silverstripe/silverstripe-cms/actions/runs/3726652553/jobs/6320241058
Note
Requires silverstripe/silverstripe-framework#10635 as well, as the affected behat tests also include interacting with tree dropdowns.
Parent issue