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 edgeql-go generates private query functions and return types. The user can export these types but it requires a few lines of code for each query. There should be a way to make the generator generate public instead of private functions and types.
Maybe this should be configurable on a per query basis?
The text was updated successfully, but these errors were encountered:
I would default to being public, if a user really wants to keep it private he can place it under an internal directory so that it's public to external packages.
chirino
added a commit
to chirino/edgedb-go
that referenced
this issue
May 5, 2024
* -pubtypes make the generated types public
* -pubfuncs makes the generated functions public
* -jsontag add a `json:”...”` field tag
Signed-off-by: Hiram Chirino <hiram@hiramchirino.com>
I would default to being public, if a user really wants to keep it private he can place it under an internal directory so that it's public to external packages.
Public by default seems reasonable, but I think there should still be a way to make them private to a package. In a large enough project it is reasonable to want to restrict some things more than just internal/.
Currently
edgeql-go
generates private query functions and return types. The user can export these types but it requires a few lines of code for each query. There should be a way to make the generator generate public instead of private functions and types.Maybe this should be configurable on a per query basis?
The text was updated successfully, but these errors were encountered: