-
Notifications
You must be signed in to change notification settings - Fork 327
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
Avoid auto initialising initAll and export Components #759
Conversation
does this require a change in our docs? |
fc68175
to
657c703
Compare
@igloosi sorry, I got sidetracked, this now includes docs and changelog updates. |
Ensures the user is in control over when the JavaScript executes. Allows users to execute the components individually, from the browser bundle.
657c703
to
9060290
Compare
Since documenting this way to include JavaScript is a bigger task I've raised an issue: #757 This is since I want to add docs on how to bring the build in from npm, similar to how we're doing it on the Prototype Kit. |
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.
💯
'Radios' | ||
]) | ||
}) | ||
it('exported Components can be initialised', async () => { |
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.
Great test! 💯
Ensures the user is in control over when the JavaScript executes.
Allows users to execute the components individually, from the
browser bundle.