-
Notifications
You must be signed in to change notification settings - Fork 842
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
Export drag and drop service methods #2377
Export drag and drop service methods #2377
Conversation
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. Only question would be if we want to export these with less generic names...
@thompsongl yeah that's a good call; we don't have a strong precedent here (TBH not even a weak one). They don't need to be discoverable except through the docs, so I'm thinking something like |
No strong preference on what the names are. I think the |
I'd continue with the |
I've updated the method names to |
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.
Thanks!
* Export move, copy, and reorder drag-and-drop service methods * changelog * Update dnd service method names
Summary
Fixes #2372 by exporting the
copy
,move
, andreorder
drag-and-drop service methods. I tested by building EUI with this change andrequire
ing the built package into node, verifying the three methods exist as expected.Checklist
- [ ] Checked in dark mode- [ ] Checked in mobile- [ ] Checked in IE11 and Firefox- [ ] Props have proper autodocs- [ ] Added documentation examples- [ ] Added or updated jest tests- [ ] Checked for accessibility including keyboard-only and screenreader modes