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
Right now the Building Modules > Recommended Module Structure advocates to put all type definitions into root module folder, while this is almost never possible due to circular references between module package and keeper package (module.go in root package needs reference to keeper, and keeper needs references to almost all module types defined in root package).
Besides that, never seen any module that follows these pattern, I suppose exactly due to this reason. All modules keep using separate types package instead of placing type definitions inside root folder.
The text was updated successfully, but these errors were encountered:
Right now the
Building Modules > Recommended Module Structure
advocates to put all type definitions into root module folder, while this is almost never possible due to circular references between module package and keeper package (module.go
in root package needs reference to keeper, and keeper needs references to almost all module types defined in root package).Besides that, never seen any module that follows these pattern, I suppose exactly due to this reason. All modules keep using separate
types
package instead of placing type definitions inside root folder.The text was updated successfully, but these errors were encountered: