-
Notifications
You must be signed in to change notification settings - Fork 2
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
Doesn't work on haxe 3.2.1 #2
Comments
It seems that this keyword has been allowed in haxe 3.3. Since I work with nightly builds I didn't noticed that. |
Agreed. There are other problems as well. I suggest putting the whole extern kit libraries under |
I also know about these issues. In a first hand, changing all packages should solve lots of issues. Some ideas: import externkit.js.aws.cognito.Cognito;
// or
import ekt.js.aws.cognito.Cognito;
// or
import aws.js.cognito.Cognito;
// or
import externkit.aws.cognito.Cognito;
// or
import extkit.aws.cognito.Cognito;
// or
import aws.cognito.Cognito; Personally, I prefer the last case. What's your opinion? |
I prefer fullnames (unless really common terms like aws), so ekt, extkit are ruled out |
Fails with
src/js/extern/Extern.hx:10: characters 15-21 : Unexpected extern
The only reason I can think of is that the keyword
extern
is not allowed as package name...The text was updated successfully, but these errors were encountered: