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
I don't want to go all in with Java-like getters and setters. I want to treat my Dto's more like JSON objects thus I would like to define field in properties:
I know that this is anti-pattern in OOP, but I don't care, my API is mostly readonly and I use the classes as a type safer alternative for typical spaghetti mixed array code.
I also don't seem to find a way to do this myself without forking graphqlite. The MagicFields are for classes, Field is for methods, and if I implement FromSourceFieldsInterface I should have to make another external class (it's not usable on the e.g. Product above directly.)
Activity
oojacoboo commentedon Mar 18, 2020
We've made use of only properties with our input types. It works well. I know that's not the same thing, but I could see how this would be valuable.
moufmouf commentedon Jun 19, 2020
Implementation pending in #269
oojacoboo commentedon Mar 29, 2021
#269 is merged in now - closing this