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 netlify build in master and add build checks #2405

Merged
merged 1 commit into from
Oct 18, 2019

Conversation

robwalch
Copy link
Collaborator

@robwalch robwalch commented Oct 15, 2019

This PR will...

  • Add "sanity-check" package script
  • Run docs in travis build and precommit
  • Fix type check errors
  • Fix bandwidth estimator tests that fail on Mac desktop because of float precision

Why is this Pull Request needed?

These changes are to help ensure we don't break netlify builds when making changes, and are necessary to generate a release with a demo page.

The sanity-check target is one I run a lot locally so I made a shortcut for it.

These changes have already been made in feature/v1.0.0.

Checklist

  • changes have been done against master branch, and PR does not conflict
  • N/A new unit / functional tests have been added (whenever applicable)
  • N/A API or design changes are documented in API.md


npm run lint
npm run type-check
npm run docs
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we need to generate docs on every commit? I say no.

If it's to check that it works, we should add a Github action / travis check that the docs build and let the CI run it.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

OK. That was overzealous of me. npm run docs is out.

Run docs in travis build
Fix type check errors
@robwalch robwalch merged commit 06b86ea into master Oct 18, 2019
@robwalch robwalch deleted the bugfix/sanity-checks branch October 18, 2019 01:56
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

Successfully merging this pull request may close these issues.

2 participants