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
Right now, instantiate is limited to methods. This doesn't work very well in kotling, as functions are not used in the same way they are in java. I think some possible additions to allow for different ways of using the API are:
Be able to annotate variables with the annotation and have that work
Expose a function from the api to inject variables, bypassing the instantiate annotation entirely.
The text was updated successfully, but these errors were encountered:
Completely agree with the first one, could you give a use-case/example of the latter as struggling to quite grasp what you mean, thanks
Right now, the variables being added to the map are hidden in one massive method. Instead, put it in its own method that can be accessed. Then, a developer could, for example:
Right now, instantiate is limited to methods. This doesn't work very well in kotling, as functions are not used in the same way they are in java. I think some possible additions to allow for different ways of using the API are:
The text was updated successfully, but these errors were encountered: