New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve Explicitly Exported Plugin Rules #99
Resolve Explicitly Exported Plugin Rules #99
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice stuff 🎉.
Let's add a few more tests and then we can get this merged.
e24d7cf
to
2f752a3
Compare
2f752a3
to
1bdb23c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eagerly waiting for #99 (comment).
1bdb23c
to
c19c638
Compare
@nikku I separated the changes into one commit that refactors the existing tests before the new feature is added by a second commit. Hopefully, that's easier to review. |
@nikku I added a commit testing the compilation of local configs. It was indeed missing. Feel free to squash. |
@philippfromme This looks simple enough now. Added the discussed improvements: Check it out, give me a 👍 and I'll do a final PR cleanup before merging it. |
Let me have a quick look! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Let's 🚢 it!
744ac4a
to
a20a257
Compare
@philippfromme a20a257 should wrap up this topic. |
This adds the ability to ship rules in a non-default location, exported through the plug-in main entry: ```javascript module.exports = { rules: { 'foo': 'src/foo', 'bar': 'src/bar' } }; ``` The location will be interpreted local to the package root.
0c477d9
to
eb7445a
Compare
I verified it works with bpmnlint-plugin-camunda-compat. |
Awesome :). |
Will go ahead and release this. |
Never mind. This worked great here but utterly fails on |
Gives plugin authors the freedom to choose their own plugin structure (cf. camunda/bpmnlint-plugin-camunda-compat#87).
Example:
Similar to ESLint, just supporting path references over
require
calls; require calls cannot easily be bundled for the browser, cf. #99 (comment), #99 (comment).Related to camunda/bpmnlint-plugin-camunda-compat#87