Skip to content

Unit test JS library resolution #1606

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

Closed
gzm0 opened this issue Apr 23, 2015 · 2 comments
Closed

Unit test JS library resolution #1606

gzm0 opened this issue Apr 23, 2015 · 2 comments
Labels
internal Not visible to users of Scala.js (only by devs in this repo) separate repo Addressing this issue should be done in a separate repository. Closed here.

Comments

@gzm0
Copy link
Contributor

gzm0 commented Apr 23, 2015

JS library resolution is growing complex. We should start adding unit tests, especially for failure cases.

@gzm0 gzm0 added the internal Not visible to users of Scala.js (only by devs in this repo) label Apr 23, 2015
@gzm0 gzm0 self-assigned this Apr 23, 2015
@gzm0 gzm0 added this to the v0.6.3 milestone Apr 23, 2015
@gzm0 gzm0 modified the milestones: v0.6.4, v0.6.3 May 1, 2015
@gzm0 gzm0 removed their assignment May 1, 2015
@gzm0
Copy link
Contributor Author

gzm0 commented May 1, 2015

Assigning this to 0.6.4, since it requires considerable infrastructure effort.

@sjrd
Copy link
Member

sjrd commented Jun 26, 2017

Migrated to scala-js/jsdependencies#3

@sjrd sjrd closed this as completed Jun 26, 2017
@sjrd sjrd added the separate repo Addressing this issue should be done in a separate repository. Closed here. label Jun 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal Not visible to users of Scala.js (only by devs in this repo) separate repo Addressing this issue should be done in a separate repository. Closed here.
Projects
None yet
Development

No branches or pull requests

3 participants