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
Wouldn't it make sense to move the domain package to engine/internal?
When the go command sees an import of a package with internal in its path, it verifies that the package doing the import is within the tree rooted at the parent of the internal directory.
The text was updated successfully, but these errors were encountered:
Possibly, although in real apps I often have other services that make use of the same domain structs so it's useful being able to pull them in to those.
Wouldn't it make sense to move the domain package to
engine/internal
?When the go command sees an import of a package with internal in its path, it verifies that the package doing the import is within the tree rooted at the parent of the internal directory.
The text was updated successfully, but these errors were encountered: