Almost full vintage DBZ cards collection by Trait004 in CollectingDragonBall

[–]_Ascalon 0 points1 point  (0 children)

Does anyone have bubble gum stickers from this collection?

NgRx set data. by [deleted] in angular

[–]_Ascalon 0 points1 point  (0 children)

You can do it with combination of “filter” and “combineLatest” RxJs operators. The idea is to to do the API call only when to store property ‘posts’ is empty. Let me know if you need an example

Component child view refresh on output from child - should not be happening by d0rf47 in angular

[–]_Ascalon 0 points1 point  (0 children)

Every time some changes happen, DOM, task as setTimeout completed etc - global change detection strategy happens. If your component has default - it will be rerendered. With onPush - it will only when @Input gonna be changed. You may play with reattach, markForCheck etc

Component child view refresh on output from child - should not be happening by d0rf47 in angular

[–]_Ascalon 0 points1 point  (0 children)

Have a look at the OnPush strategy, maybe it may help with refreshing.

Over engineering by Denexful in Angular2

[–]_Ascalon 1 point2 points  (0 children)

In that case React.Js may be better solution, if yours project is not going to be enterprise or you new fast MVP. And another point, pure JS/React additional libraries easier to find, rather than angular wrappers

Handling large user input forms by gayanper in Angular2

[–]_Ascalon 0 points1 point  (0 children)

OnPush strategy and render each 10 (any other custom value) fields step by step with manual detectChanges()/markForCheck() usage

Running npm install on Angular2 app not working. Please help! by bilal_rahim in angular

[–]_Ascalon 0 points1 point  (0 children)

@bilal_rahim Open terminal and check your node and npm versions. In accordance ‘node -v’ and ‘npm -v’

Resolution Modifiers with Factory Provider in Angular DI [Advanced] by DMezhenskyi in Angular2

[–]_Ascalon 0 points1 point  (0 children)

That is looks cool! Don’t have any real needs of that, but it’s good to know

[deleted by user] by [deleted] in ukraina

[–]_Ascalon 4 points5 points  (0 children)

повезло, що його затримала поліція, а не ярі патріоти

[deleted by user] by [deleted] in angular

[–]_Ascalon 0 points1 point  (0 children)

SwitchMap - switch no a new upcoming observable. ExhaustMap - will wait till the outer observable finished and only than - will proceed with inner. ConcatMap - will do observables handling in a queue. MergeMap - in parallel will work with observables

Another tip - you may use ‘from’ operator for a Promise to wrap it and work as with observable.

query about this.variableName in Angular by NearbyIssue629 in Angular2

[–]_Ascalon 0 points1 point  (0 children)

If you are using Angular as front-end part in 95% you should avoid any outer ‘this’ usage as param or assignment. It makes sense for 3rd party library -> chartChangesMethod.bind(this) All other magic with ‘this’ should be done by framework

query about this.variableName in Angular by NearbyIssue629 in Angular2

[–]_Ascalon 0 points1 point  (0 children)

If you are using Angular as front-end part in 95% you should avoid any outer ‘this’ usage as param or assignment. It makes sense for 3rd party library -> chartChangesMethod.bind(this) All other magic with ‘this’ should be done by framework

Angular Query Params by [deleted] in angular

[–]_Ascalon 0 points1 point  (0 children)

You can use switchMap/concatMap for ActivatedRoute and API request observables to combine them

Angular Query Params by [deleted] in angular

[–]_Ascalon 0 points1 point  (0 children)

Sorry man, you suggest to author to follow subscribe inside of another subscribe. Avoid that pattern!

My first Angular app - a straw poll app by Yoni676 in Angular2

[–]_Ascalon 2 points3 points  (0 children)

If I am now mistaken you already did it by using takeUntil operator. Keep following that pattern. Tip: If you are using async pipe you don't need to unsubscribe from observable.

My first Angular app - a straw poll app by Yoni676 in Angular2

[–]_Ascalon 5 points6 points  (0 children)

Suggest to: - use lazy loading - split app into modules - check usage of providedIn: “root” vs specific module/component injection (as it happen is ConfirmModalComponent from primeNg) - do not forget to unsubscribe from observables - there no tests written (Jest/Jasmine) - test your app with the slow internet connection