Publish dxDiagram types, arrange "commands" props types (T1227506) #27344
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-picks
Changelog:
@public
+@namespace DevExpress.ui.dxDiagram
(with thedxDiagram
scope - to avoid naming conflicts in a bundle similar to the other components)@public
(@namespace DevExpress.ui
already exists - no thedxDiagram
scope - the type name already starts withdxDiagram
, i.e., an unique / component-basis prefix), interface -> type(dx)Diagram
prefixAll published types become available in framework packages re-exports
Array<dxDiagramCustomCommand>|Array<Enums.DiagramCommand>
- now have this type in d.ts (Array<CustomCommand | Command>
) without doc tag override (note that in react we cannot add a real enum / union type import, but use indi acc values instead, otherwise - BC)as any
Docs:
DevExpress/devextreme-documentation#6302
DevExpress/devextreme-documentation#6322