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
The biggest complaint I've heard from people I've talked to who use hugsql is that jump-to-definition functions stop working as soon as they hit a hugsql-generated function.
It looks like hugsql uses a source-logging-push-back-reader which is capable of tracking line numbers and filenames. Attaching this metadata to the vars created by hugsql would allow existing tooling to be able to jump straight to the .sql files from which they are defined.
The text was updated successfully, but these errors were encountered:
The biggest complaint I've heard from people I've talked to who use hugsql is that jump-to-definition functions stop working as soon as they hit a hugsql-generated function.
It looks like hugsql uses a
source-logging-push-back-reader
which is capable of tracking line numbers and filenames. Attaching this metadata to the vars created by hugsql would allow existing tooling to be able to jump straight to the.sql
files from which they are defined.The text was updated successfully, but these errors were encountered: