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
If names were specified then get_code used get_code_dependencies. This was meant to work on qenv class, that's why it was developed in teal.code. However, we then removed it, so that we do not change too much in the user interface. We specifically left get_code_dependencies non-exported, so that it could be only used in teal.data::get_code.teal_data in the future.
If we plan to let it work only on teal_data which is introduced in teal.data I think it's fine enough to move get_code_dependencies from teal.code to teal.data.
Even though get_code_dependencies works on character input, it is designed to work on teal_data@code.
We once had
get_code(qenv, names)
in the prototype phase of code parser insightsengineering/teal.code#133.If
names
were specified thenget_code
usedget_code_dependencies
. This was meant to work onqenv
class, that's why it was developed inteal.code
. However, we then removed it, so that we do not change too much in the user interface. We specifically leftget_code_dependencies
non-exported, so that it could be only used inteal.data::get_code.teal_data
in the future.If we plan to let it work only on
teal_data
which is introduced inteal.data
I think it's fine enough to moveget_code_dependencies
fromteal.code
toteal.data
.Even though
get_code_dependencies
works oncharacter
input, it is designed to work onteal_data@code
.Potentially improve with #192
The text was updated successfully, but these errors were encountered: