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

onCloned #34

Open
dalholm opened this issue May 8, 2020 · 1 comment
Open

onCloned #34

dalholm opened this issue May 8, 2020 · 1 comment

Comments

@dalholm
Copy link

dalholm commented May 8, 2020

i dont know if i understand it wrong, but onCloned is called to early and also it should have the new model as an argument.

When i clone a model with relations after its cloned i want change some of the data on the new relation. But the new relation is not yet cloned neither

@Putr
Copy link
Contributor

Putr commented Aug 28, 2020

I can confirm that this bug report.

When onCloned is called relationships are not yet available.

Putr added a commit to Putr/cloner that referenced this issue Aug 28, 2020
This should fix the BKWLD#34 issue where onCloned is called too early.
@Putr Putr mentioned this issue Aug 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants