Refactoring: stack type goes better in a separate library #278
Labels
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
refactor
Milestone
Since the stack type is generic and not necessarily related to capability we could use a different package to hold those types an allow it to be imported from multiple other points or even externally since it's pretty useful for many cases. Instead of having it on internal/capabilities/types.go we could provide a different package not sure what name and what this package could hold though.
The text was updated successfully, but these errors were encountered: