Early module implementation #1
Merged
Conversation
This file contains 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
This was referenced Apr 6, 2022
Merged
t3chguy
reviewed
Apr 18, 2022
t3chguy
reviewed
Apr 18, 2022
turt2live
force-pushed
the
travis/modules
branch
from
e000ac6 to
48a7ef5
Compare
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.
This contains the bare minimum to demonstrate how a module API might work. Other modules may be more complex, but would see a similar setup.
At the moment, this is not formally tested. Testing these sorts of things is complicated and best suited for a future PR due to shear size.
The intent is that the module has the tests to make sure it works within an Element Web, using some sort of Cypress-like setup.
Part of a series: