We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now copying from the nested view does add the new element to the old parent, e.g. a copied section does not end up in the same catalog.
Copying elements should add them to the same parent.
The parent needs to be a prop to the element component (e.g. here https://github.com/rdmorganiser/rdmo/blob/main/rdmo/management/assets/js/components/nested/NestedCatalog.js#L94) and then needs to be provoded to fetchCopy (https://github.com/rdmorganiser/rdmo/blob/main/rdmo/management/assets/js/components/element/Section.js#L29). Prferebly in the same format as for the createSection action ({ catalog }) so that the same syntax as in the factories can be used.
fetchCopy
createSection
{ catalog }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description / Beschreibung
Right now copying from the nested view does add the new element to the old parent, e.g. a copied section does not end up in the same catalog.
Expected behaviour / Erwartetes Verhalten
Copying elements should add them to the same parent.
Ideas
The parent needs to be a prop to the element component (e.g. here https://github.com/rdmorganiser/rdmo/blob/main/rdmo/management/assets/js/components/nested/NestedCatalog.js#L94) and then needs to be provoded to
fetchCopy
(https://github.com/rdmorganiser/rdmo/blob/main/rdmo/management/assets/js/components/element/Section.js#L29). Prferebly in the same format as for thecreateSection
action ({ catalog }
) so that the same syntax as in the factories can be used.The text was updated successfully, but these errors were encountered: