this way resource stores all the resources in the same format as other resources (such as auth, socket, persistence, github, template, etc) can store subresources. this way we can implement docs, package, etc to iterate through subresources.
the proposed name of a subresource is parent-child as in auth-github. (or does auth::github make more sense?) the proposed way to access a subresource is parent.child as in auth.github, which should be reflected when generating documentation.
this way
resourcestores all the resources in the same format as other resources (such asauth,socket,persistence,github,template, etc) can store subresources. this way we can implementdocs,package, etc to iterate through subresources.the proposed name of a subresource is
parent-childas inauth-github. (or doesauth::githubmake more sense?) the proposed way to access a subresource isparent.childas inauth.github, which should be reflected when generating documentation.