-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fix: send override fields #19
Conversation
Hmm, need to think about this. One option is to cleanup every time and hold this state on the backend. What do we do currently with optimization policy? And do we keep any other state on the frontend?
I think that just execute is needed. |
@odjuricicTT we don't keep any other state on the frontend, just the changes to fields and the optimization policy. For optimization policy, we don't cleanup the value. But I think for overwritten fields it makes sense to cleanup changes as those would be applied when the model is executed, no? |
Add the
changes
field to theexecute
request as well as theconvert
request send after executing the model.Questions still to be answered:
convert
andexecute
?