Skip to content
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

Remove need for init #16

Open
asbjornu opened this issue Jul 13, 2018 · 2 comments
Open

Remove need for init #16

asbjornu opened this issue Jul 13, 2018 · 2 comments
Labels
enhancement New feature or request

Comments

@asbjornu
Copy link
Contributor

Right not it's necessary to invoke .init() to initialize components. As discussed on Slack, Bootstrap does not require this, so we shouldn't either.

@erikhallaraaker
Copy link
Contributor

erikhallaraaker commented Jul 13, 2018

As per now the only time you NEED to run the init functions manually is if you are building a SPA. With regular routing the components will initialize themselves.

But I agree that this should be fixed for SPA's as well. I am looking into a solution for that

@erikhallaraaker erikhallaraaker added the enhancement New feature or request label Oct 5, 2018
@johnhaavardstun
Copy link

As an intermediate improvement, you could consider noting in the docs for which components you would need to manually invoke .init().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants