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

Feature/126 #133

Merged
merged 5 commits into from
Nov 19, 2019
Merged

Feature/126 #133

merged 5 commits into from
Nov 19, 2019

Conversation

filippomc
Copy link
Contributor

  • Add coverage for whatever new functionality, to a JUnit test if it's backend, to a Casper Test if it's frontend
  • Make sure both push and pr travis builds are passing before asking for a review

@filippomc
Copy link
Contributor Author

@rodriguez-facundo is this ready to merge?

@rodriguez-facundo
Copy link
Member

It is bumping three from 87 to 110... I don't feel comfortable with that. But @tarelli said "if tests are passing, it is ok".

What if I try to come back to 87 and see if it works now that I removed the problematic package react-forcegraph-vr @filippomc

@rodriguez-facundo
Copy link
Member

Went back to THREE v 0.87.1. This is ready to be merged.

@filippomc filippomc requested a review from tarelli November 19, 2019 09:52
@tarelli tarelli merged commit 4f69841 into development Nov 19, 2019
@filippomc filippomc deleted the feature/126 branch November 19, 2019 15:16
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.

3 participants