Draft
Conversation
There is a ton of boilerplate in modules My experience is that there is just so much it makes it harder than necessary to write one and/or miss a field that should be updated Start by cleaning up unused methods
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've always felt that module setup is a bit verbose.
With the recent complaints about module contributions have friction, I wanted to take a crack at drying up the boilerplate a bit in order to reduce problems I have seen when building modules.
I think there are some opportunities for cleaning up the following as well, but I'll need to restretch my legs:
Notes & Caveats
Some part of this change does seem to have somehow broken the multiple module