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

Dropdown's are not reactive in Example Forum #105

Open
drpears opened this issue Dec 31, 2018 · 10 comments
Open

Dropdown's are not reactive in Example Forum #105

drpears opened this issue Dec 31, 2018 · 10 comments

Comments

@drpears
Copy link

drpears commented Dec 31, 2018

I'm using the Example Forum package and am seeing the warning below in the console along with the Dropdown component being non responsive.
image

Here's a screen record of the non responsive behavior Uploaded Video

There's no warnings or errors thrown in the console related to this issue. I would debug further but it seems that it's a core vulcan ui component and I'm not to familiar with the entirety of the architecture yet.

I appreciate any help, thanks!

Dylan

@SachaG
Copy link
Contributor

SachaG commented Jan 1, 2019

Looks like an error due to the recent react-bootstrap/Bootstrap 4 update. I'll look into it, thanks!

@drpears
Copy link
Author

drpears commented Jan 2, 2019

@SachaG great thank you

@SachaG
Copy link
Contributor

SachaG commented Jan 2, 2019

Should be fixed; I just need to push a new version (1.12.13) of the core Vulcan packages and it should be fine :)

@drpears
Copy link
Author

drpears commented Jan 4, 2019

@SachaG Updated the core packages to 1.12.13 and I'm still seeing an issue with the bootstrap related components. Could you point me to which of the core packages I could take a look at and debug?

@SachaG
Copy link
Contributor

SachaG commented Jan 4, 2019

You can search the codebase for whatever component is creating the issue but generally they'll all be in the bootstrap-ui package.

@SachaG
Copy link
Contributor

SachaG commented Jan 4, 2019

Of course you can post your issues here, too.

@drpears
Copy link
Author

drpears commented Jan 5, 2019

@SachaG Did the changes you made when you pushed to 1.12.13 fix it on your side?

@SachaG
Copy link
Contributor

SachaG commented Jan 5, 2019

Yes but you also have to pull the latest changes from this repo.

@yairtal
Copy link

yairtal commented Feb 3, 2019

Try cloning the repo again and then:
meteor update
yarn install
yarn start

@lcfd
Copy link

lcfd commented Feb 11, 2019

I'm using the getting-started-completed branch, it's kinda working, try it

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

No branches or pull requests

4 participants