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
In this period we have wrote already some contract in slangroom and one of the thing that I didn't really like was the fact that, in contrast to restroom, slangroom accept only data via data or keys and not inline. In particular when moving elements from one object to another one all the path had to be specified in the keys, making them quite big and noisy, for example see here.
We also noticed that old restroom db statement that save a variable in a table save them under the key that is their name, but in slangroom we can not do that (we solve it for the moment by passing the name also as a variable).
The final question that raise is: should we enlarge slangroom to store and then have the possibility to read inline data, with functions ctx.fetchName() and ctx.getName() (or something similar), to be used where this can improve usability of the code?
The text was updated successfully, but these errors were encountered:
In this period we have wrote already some contract in slangroom and one of the thing that I didn't really like was the fact that, in contrast to restroom, slangroom accept only data via data or keys and not inline. In particular when moving elements from one object to another one all the path had to be specified in the keys, making them quite big and noisy, for example see here.
We also noticed that old restroom db statement that save a variable in a table save them under the key that is their name, but in slangroom we can not do that (we solve it for the moment by passing the name also as a variable).
The final question that raise is: should we enlarge slangroom to store and then have the possibility to read inline data, with functions
ctx.fetchName()
andctx.getName()
(or something similar), to be used where this can improve usability of the code?The text was updated successfully, but these errors were encountered: