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

Outdated URI in import or part statements #42

Closed
crelier opened this issue Mar 2, 2016 · 3 comments
Closed

Outdated URI in import or part statements #42

crelier opened this issue Mar 2, 2016 · 3 comments
Assignees
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue

Comments

@crelier
Copy link

crelier commented Mar 2, 2016

The URI in import or part statements need to be updated in these tests:
Language/Libraries_and_Scripts/URIs/syntax_t04
Language/Libraries_and_Scripts/URIs/syntax_t05
Language/Libraries_and_Scripts/URIs/syntax_t09
Language/Libraries_and_Scripts/URIs/syntax_t10
Language/Libraries_and_Scripts/URIs/syntax_t14
Language/Libraries_and_Scripts/URIs/syntax_t15

@sgrekhov sgrekhov self-assigned this Mar 3, 2016
@sgrekhov sgrekhov added the type-question A question about expected behavior or functionality label Mar 3, 2016
@sgrekhov
Copy link
Contributor

sgrekhov commented Mar 3, 2016

@crelier I don't see any outdated URI in these tests (at least in the latest version of co19 tests). Please clarify what's wrong with these tests

@crelier
Copy link
Author

crelier commented Mar 3, 2016

This must be the same problem as for #39 and #40. Our version is behind and needs updating.
One example, in Language/Libraries_and_Scripts/URIs/syntax_t04, I see:
import "5_Library1" ".dart";

@sgrekhov sgrekhov added closed-not-planned Closed as we don't intend to take action on the reported issue and removed type-question A question about expected behavior or functionality labels Mar 4, 2016
@sgrekhov
Copy link
Contributor

sgrekhov commented Mar 4, 2016

Ok. No this issue in the current version of co19 tests

@sgrekhov sgrekhov closed this as completed Mar 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue
Projects
None yet
Development

No branches or pull requests

2 participants