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
Integrate dartanalyzer into build #2
Comments
This was referenced Jun 18, 2015
goderbauer
added a commit
to goderbauer/angular
that referenced
this issue
Aug 7, 2015
This fixes the following type error that is thrown when calling getAllAngularTestability() while running Dartium in checked mode: type 'MappedListIterable' is not a subtype of type 'List<PublicTestability>' of 'publicTestabilities'. #0 GetTestability.addToWindow.<anonymous closure> (package:angular2/src/core/testability/get_testability.dart:92:12) #1 Function._apply (dart:core-patch/function_patch.dart:7) angular#2 Function.apply (dart:core-patch/function_patch.dart:28) angular#3 __invokeFn (package:angular2/src/core/testability/get_testability.dart:26:26) angular#4 _jsFunction.<anonymous closure> (package:angular2/src/core/testability/get_testability.dart:15:12)
This was referenced Aug 7, 2015
This was referenced Mar 3, 2016
6 tasks
ottonascarella
pushed a commit
to ottonascarella/angular
that referenced
this issue
Feb 20, 2018
# This is the 1st commit message: fix(common): inconsistency on TitleCasePipe TitleCasePipe was not behaving as expected with non-ascii characters. # This is the commit message angular#2: refactor(common): lint errors # This is the commit message angular#3: feat(common): more tests for TitleCasePipe Copied tests from angular#20123, just to make sure fix covers all needs. # This is the commit message angular#4: refactor(common): fix linting errors
3 tasks
3 tasks
lucasklaassen
added a commit
to lucasklaassen/angular
that referenced
this issue
Oct 30, 2018
alxhub
referenced
this issue
in alxhub/angular
Dec 5, 2018
Previously the ngfactory shim generator in ngtsc would always write two imports in the factory file shims: 1) an import to @angular/core 2) an import to the base file If the base file has no exports, import #2 would be empty. This turns out to cause issues downstream. This commit changes the generated shim so if there are no exports in the base file, the generated shim is empty too.
alxhub
referenced
this issue
in alxhub/angular
Dec 5, 2018
Previously the ngfactory shim generator in ngtsc would always write two imports in the factory file shims: 1) an import to @angular/core 2) an import to the base file If the base file has no exports, import #2 would be empty. This turns out to cause issues downstream. This commit changes the generated shim so if there are no exports in the base file, the generated shim is empty too.
IgorMinar
referenced
this issue
in alxhub/angular
Dec 5, 2018
Previously the ngfactory shim generator in ngtsc would always write two imports in the factory file shims: 1) an import to @angular/core 2) an import to the base file If the base file has no exports, import #2 would be empty. This turns out to cause issues downstream. This commit changes the generated shim so if there are no exports in the base file, the generated shim is empty too.
IgorMinar
pushed a commit
that referenced
this issue
Dec 5, 2018
Previously the ngfactory shim generator in ngtsc would always write two imports in the factory file shims: 1) an import to @angular/core 2) an import to the base file If the base file has no exports, import #2 would be empty. This turns out to cause issues downstream. This commit changes the generated shim so if there are no exports in the base file, the generated shim is empty too. PR Close #27470
FrederikSchlemmer
pushed a commit
to FrederikSchlemmer/angular
that referenced
this issue
Jan 3, 2019
Previously the ngfactory shim generator in ngtsc would always write two imports in the factory file shims: 1) an import to @angular/core 2) an import to the base file If the base file has no exports, import angular#2 would be empty. This turns out to cause issues downstream. This commit changes the generated shim so if there are no exports in the base file, the generated shim is empty too. PR Close angular#27470
ngfelixl
pushed a commit
to ngfelixl/angular
that referenced
this issue
Jan 28, 2019
Previously the ngfactory shim generator in ngtsc would always write two imports in the factory file shims: 1) an import to @angular/core 2) an import to the base file If the base file has no exports, import angular#2 would be empty. This turns out to cause issues downstream. This commit changes the generated shim so if there are no exports in the base file, the generated shim is empty too. PR Close angular#27470
14 tasks
14 tasks
14 tasks
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
this implies we need angular.dart file which looks something like this:
Don't generate that, but we need something like this as public API.
The text was updated successfully, but these errors were encountered: