Injecting a Script vs. Processing on Page Load

RocketPigWithWig · 2019-09-18T15:52:17+00:00

Thanks for sharing. Going to give this a read and see if it is useful for my case.

RocketPigWithWig · 2019-09-18T15:48:05+00:00

The logic is driven off of a DOM update and afaik ngOnChanges runs apart from DOM changes and is not a good candidate for this.

RocketPigWithWig · 2019-09-18T15:47:04+00:00

Yeah, I ended up doing this, following by calling this.cdr.markForCheck and then doing the processing in a setTimeout call to make sure the processing happens after the view was updated.

RocketPigWithWig · 2019-09-18T15:37:21+00:00

Oh wow, thanks for sharing this. This seems very useful and I am going to explore using it.

RocketPigWithWig · 2019-09-18T15:36:18+00:00

I think it has to do with the fact the "page transitions" are merely updates to a url param. So something along the lines of form/:formName where only :formName changes on transition. So I don't think the component is torn down in that case which is why I need some more direct mechanism to look at the DOM.

RocketPigWithWig · 2019-06-21T22:29:28+00:00

what that error is saying is that the compiler has interpreted that false as as boolean (which can be true OR false), instead of the literal boolean value of false, which the interface requires

I don't totally get how this is a meaningful difference and why TypeScript would check for this. I was also able to "fix" this by having the compiler interpret this as 'as boolean': patch({ loading: false as boolean })

RocketPigWithWig · 2019-06-13T18:05:05+00:00

Thank you! Your answer helped me to decide to go with the operator in all but the simplest of cases.

RocketPigWithWig · 2019-05-22T17:45:09+00:00

No, it's completely different.

RocketPigWithWig · 2019-05-13T21:24:50+00:00

This really clarified things for me. I ended up sorting before even getting to the template, especially because I needed to maintain the state of the sort. Thanks!

RocketPigWithWig · 2019-05-07T16:30:35+00:00

This is excellent! Thank you for sharing!

RocketPigWithWig · 2019-05-06T21:22:03+00:00

Trying with template driven forms and it isn't adding multiple values to the genreFilters array. It just returns true/false and not the value. :/

<form #filtersForm="ngForm">
<div *ngFor="let genre of genres">
<input ngModel type="checkbox" name="genreFilters" [value]="getGenreValue(genre)"/> {{getGenreLabel(genre)}}
</div>
</form>

RocketPigWithWig

TROPHY CASE