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've been finding it helpful to add write_table-type functions to automatically add a project-specific schema, and therefore would like to do things like:
However, Legolas.@row requires a hard-coded schema name there, not the MySchema variable. It would be nice if this could be generalized. I'm not sure if this is even possible because I don't know think the value of MySchema is available at macro-expansion time. But it is a pain point so I figured I'd open an issue for discussion.
The text was updated successfully, but these errors were encountered:
I don't think I hit this whenever I work with Schemas since I generally prefer "spelling" a-priori-known Schema values as literals instead of rebinding them to a const.
That being said, I'm not opposed to supporting something like this if the implementation can be sussed out
I've been finding it helpful to add
write_table
-type functions to automatically add a project-specific schema, and therefore would like to do things like:However,
Legolas.@row
requires a hard-coded schema name there, not theMySchema
variable. It would be nice if this could be generalized. I'm not sure if this is even possible because I don't know think the value ofMySchema
is available at macro-expansion time. But it is a pain point so I figured I'd open an issue for discussion.The text was updated successfully, but these errors were encountered: