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
Currently if the output of two generated queries are the same the output type is re-used, though the name seems to fit the first function that used that type.
This leads to problems when changing one of the queries using that output. The output type will change, so imports using it will break.
Since I prefer to typehint most of my applications whenever I change an existing query I have to change unrelated code that used the same output types. The name being unrelated to the query also ends up really awkward at times.
A current example: I have two unrelated models that both have queries that output `{id, name}'. Because I just dropped an output from one of them, they both now use that pattern, so the output is named after the output of another table.
Thanks!
The text was updated successfully, but these errors were encountered:
Currently if the output of two generated queries are the same the output type is re-used, though the name seems to fit the first function that used that type.
This leads to problems when changing one of the queries using that output. The output type will change, so imports using it will break.
Since I prefer to typehint most of my applications whenever I change an existing query I have to change unrelated code that used the same output types. The name being unrelated to the query also ends up really awkward at times.
A current example: I have two unrelated models that both have queries that output `{id, name}'. Because I just dropped an output from one of them, they both now use that pattern, so the output is named after the output of another table.
Thanks!
The text was updated successfully, but these errors were encountered: