Jarek Rencz
Jarek Rencz
I just bumped into this myself :) It seems like the way to go (at least until anything related to zones is expected) is to unify the "route as string"...
### Briefly I tend to think it's rather an CloudFront API issue than JS SDK issue. Or that there's some coincidence of those requests being sent interlaced with some other...
this way it will not be backwards compatible (although logical). IMO Either a method or on next major release
Not all functions are handled with angular DI so it would be inprecise to use just max-params. On the other hand it may be fair enough: I can't think of...
@tilmanpotthof have you had any chance of working on this feature suggestion?
This rule should also allow logic services to take named params (I mean ES2015 destructuring): ``` js .run(function ( someLogic, config ) { someLogic({ foo: 1, bar: 42 }); //...
@Gillespie59 in fact the analog of the first case is ``` js $http(...) .catch(function(){}) .then(function(){}) ``` I think this rule is more general: it's not about angular, it's about promises...
I just found this issue after a of of investigation of some problem I experienced in my project. I'm happy that tsconfig can be specified since https://github.com/modernweb-dev/web/pull/1922 and specifying it...
@Stradivario take a look at `rollup-plugin-typescript-paths` I use it and it does the job
@electrovir you need to pass the tsconfig part next to `ts:true` in esbuild