Skip to content
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

Do not use copy-of for mapping a container field #1865

Open
igarashitm opened this issue Dec 16, 2024 · 0 comments
Open

Do not use copy-of for mapping a container field #1865

igarashitm opened this issue Dec 16, 2024 · 0 comments
Labels
bug Something isn't working DataMapper All issues related to the DataMapper functionality

Comments

@igarashitm
Copy link
Contributor

igarashitm commented Dec 16, 2024

Describe the Bug

It only works if both source and target are completely same including namespace, which we can't expect for data mapping. We should instead construct parent structures and then put value-of for the terminal fields.

#1780 and #1846 are related. If we don't use copy-of and construct the container structure, we might be able to do a bit more flexible mapping, for example if source side and target side has different children, only map the children that has the same name. And topmost parent name doesn't have to be same on source and target.

Steps to Reproduce the Bug or Issue

  1. DnD container field

Screenshots or Videos

No response

Platform

  • OS: [e.g. macOS, Windows, Linux]
  • Browser: [e.g. Chrome, Safari, Firefox]
  • Version: [e.g. 0.30.0]
@igarashitm igarashitm added bug Something isn't working functionality DataMapper All issues related to the DataMapper labels Dec 16, 2024
@igarashitm igarashitm moved this from New to Backlog in Kanban Board Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working DataMapper All issues related to the DataMapper functionality
Projects
Status: Backlog
Development

No branches or pull requests

1 participant