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

Fix docs app by upgrading dependencies #1514

Merged
merged 3 commits into from May 19, 2021

Conversation

jelhan
Copy link
Contributor

@jelhan jelhan commented May 18, 2021

This includes:

  • Upgrade ember-source and ember-cli
  • Upgrade blueprints to 3.26.1
  • Upgrade ember-bootstrap-power-select and ember-power-select
  • Upgrade ember-bootstrap-cp-validations

And many more.

To not require too much refactoring at once I changed some ESLint and template lint from error to warn. We should address them later.

It also prettifies the JavaScript files as Prettier is enabled by default in recent blueprints. That causes a lot of churn on the merge request. I hope review is not too hard anyways.

I think we should add basic test coverage for docs app to not end up in the same situation again. A simple check that the app could be build would have caught that problem early. But I think we can do so in a follow-up PR to not overload this one.

This includes:

- Upgrade ember-source and ember-cli
- Upgrade blueprints to 3.26.1
- Upgrade ember-bootstrap-power-select and ember-power-select
- Upgrade ember-bootstrap-cp-validations

And many more.
Copy link
Contributor

@simonihmig simonihmig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's awesome. I had this on my to do list, but really glad you did it first! 😆
Thanks so much!

It also prettifies the JavaScript files as Prettier is enabled by default in recent blueprints. That causes a lot of churn on the merge request. I hope review is not too hard anyways.

No problem. Tbh I didn't review this line by line, as there don't seem to be any controversial changes, and as I trust you any way! 😉

I think we should add basic test coverage for docs app to not end up in the same situation again. A simple check that the app could be build would have caught that problem early. But I think we can do so in a follow-up PR to not overload this one.

Makes sense! We could/should also configure dependabot to update the docs app also! (hopefully not causing separate PRs for the same dependencies! 🤔 In a real monorepo this works quite fine)

@simonihmig
Copy link
Contributor

Before the next release, I'll play with this locally. But merging this already now.

@simonihmig simonihmig merged commit c3faf04 into master May 19, 2021
@simonihmig simonihmig deleted the fix-docs-app-by-upgrading-dependencies branch May 19, 2021 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants