You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current state of collections mapping is not flexible and make a lot of troubles.
In SF 2.0 if user sets by_reference property to false, setter for collection was called, e.g. setItems().
Now (SF 2.1) if object have method addItem(), this method is called.
Lets take example with ordered items, e.g. gallery images.
User changes they order in UI and script have to reorder them in DB. To do so setImages() method should be used, but class contains also addImage() method, which is used instead and breaks the logic.
There should be an option to disable individual setter usage, when by_reference is set to false.
The text was updated successfully, but these errors were encountered:
I see most of the instances of PropertyPath are created from strings and I see no entry point to pass some configuration parameter. Can you guys give me some tips of possible parameter injection?
Current state of collections mapping is not flexible and make a lot of troubles.
In SF 2.0 if user sets by_reference property to false, setter for collection was called, e.g. setItems().
Now (SF 2.1) if object have method addItem(), this method is called.
Lets take example with ordered items, e.g. gallery images.
User changes they order in UI and script have to reorder them in DB. To do so setImages() method should be used, but class contains also addImage() method, which is used instead and breaks the logic.
There should be an option to disable individual setter usage, when by_reference is set to false.
The text was updated successfully, but these errors were encountered: