Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Compilation warning from "grunt package" #3810

Open
benmccann opened this issue Aug 30, 2013 · 6 comments
Open

Compilation warning from "grunt package" #3810

benmccann opened this issue Aug 30, 2013 · 6 comments

Comments

@benmccann
Copy link
Contributor

It would be great to fix this since it's the only warning and then make warnings into errors so that we maintain a warning-free state:

$ grunt package

build/angular.js:10124: WARNING - Throw expression is not a minErr instance.
            throw e;
            ^

0 error(s), 1 warning(s)
@btford
Copy link
Contributor

btford commented Oct 3, 2013

This is something you'd have to special-case in minErr.

PR welcome :)

@benmccann
Copy link
Contributor Author

I'm not super familiar with that. Does that mean the changes would go into the ng-closure-runner project instead of this one?

@btford
Copy link
Contributor

btford commented Oct 3, 2013

probably. @ksheedlo knows more than I do about this. :)

@ksheedlo
Copy link
Contributor

ksheedlo commented Oct 3, 2013

Right. The problem with this is it's a rethrow case. We know the code that
causes the warning throws MinErr. The exception needs to be checked and
rethrown, which confuses the compiler and causes the warning. The solution
to this is to write a new minerr pass implementation using closure compiler
type annotations. It will need work in both ng-closure-runner and angular
itself.

I've got a lot of stuff on my plate right now, but I can try and fast track
the fix so we can have it maybe before we get out of RC. A lot of folks
have asked for it.

@benmccann
Copy link
Contributor Author

Looks like we're still getting this when I run grunt

@IgorMinar
Copy link
Contributor

yes. we need to decide how to deal with rethrown exception with minErr. this is a currently unresolved problem, but it's not a significant issue so we deprioritized it.

if anyone has a proposal and wants to send a PR then that would be great.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants