john west
john west
So the css above is working above in Firefox and Chrome. It's IE11 in which it doesn't work. Any ideas?
Is there a way to suppress this?
@getsaf hey there, me again. looks like we're hitting this one, too. can't do much, but i'll owe you a cup of coffee for helping with these issues :). thx.
brandon, thank you!!! this is huge!
@getsaf Brandon, did you see this one? we're hitting up against it as we migrate to Angular 14. could you take a look? thx!
> Arrays/Indexes are safely navigated in templates but not in the way one would expect: > In TypeScript: `foo?.bar?.[0]?.quxx` > In Angular Templates: `foo?.bar[0]?.quxx` > See #13254 > and [f31c947](https://github.com/angular/angular/commit/f31c9470fae06adc69b2b665773bfc0a8a10d10e)...
since there are finite rules around how angular does optional chaining, it would be a *relatively* easy regex replace rule for the most part, right? i know, it's always easy...
fwiw, i too just ran into the max stack error in colorette while upgrading angular. the pr above with a proposed fix definitely solved the issue for me.
any update on this? there is just too much noise, an option like this would be huge. any chance of it being implemented? thx
This is the missing piece. I have been working on a poc for an app, but I can’t use wasp for the real thing because it doesn’t really support the...