ajitpanigrahi.com
Level 26 Mage / SDE3 @Fortinet
✦ For Work: Frontend Infra & Tooling, Accessibility, Design, UX
✦ For Fun: Playing bullet-hell, precision platformers
✦ https://ajitpanigrahi.com
✦ https://bento.me/ajit
24 posts
364 followers
632 following
Getting Started
Active Commenter
comment in response to
post
We have a few teams slowly rewriting Angular.js (v1) to v17 too 😂
comment in response to
post
Few teams on 12/13: stuck due to outdated dependencies
Most on 14/15: stuck due to a few ViewEngine dependencies, so can't move to 16 just yet
Few on 17: Internal UI library supports up to 17, so this is the latest we go for now. Planning for 19 after a few experimental features become stable.
comment in response to
post
I just saw someone post about Indian Railways over on LinkedIn!
They (www.irctc.co.in) use Angular 9!
comment in response to
post
The simpler mental model now: CD runs only when we programmatically update a signal used in the template or when an event is triggered, like (click)
We can expect better docs once Zoneless moves out of the experimental state. Until then, GitHub PRs are a better source of info.
comment in response to
post
While not explicitly mentioned, lifecycle hooks still work in the sense that they will execute code, but will not trigger a CD/synchronization unless a signal used in the template is updated within it.
comment in response to
post
I believe we can enforce the type when using signal inputs. This type mismatch issue exists for all decorator-based properties
comment in response to
post
Just had a quick glance, but what makes this article specifically v19+? Is it because contentChild etc. are out of dev preview?
comment in response to
post
What was your use case to get to this point and discover this? A custom error message component?
comment in response to
post
Here, using RxJs is more concise as a one-off case. If you need multiple computed properties then signals approach is better. With RxJS (w/o rxResource), you would need to use shareReplay to make it equivalent, and w/ rxResource, it behaves like toSignal anyway, and then use computed
comment in response to
post
Congratulations Corbin!
comment in response to
post
Done!
github.com/playfulprogr...
comment in response to
post
Sure!
comment in response to
post
These links should have break-word I think
comment in response to
post
*child, not cold
comment in response to
post
I feel this is justified in "super" components (smart). Like, an unstyled table component shouldn't have methods, but if I use it to make a custom table for server side pagination (or something else) and if I need a refresh() method, I would use it from the cold component or maybe with viewChild
comment in response to
post
Payload was agnostic initially (and honestly still is) but is prioritising the Next.js integration more (for marketing, I assume)
comment in response to
post
I've used CRUD mixins for Django (Python) APIs/backend, which use a mixin format for their implementation, too. It works well-ish, but I keep forgetting how I did it after a few months whenever I need a new mixin to support calling, say, GET /<base>/export instead of the regular ones
comment in response to
post
Awesome! Please add me as well! 😇
comment in response to
post
Customising a chart always feels like it needs a lot of effort (DX issue).
I tried porting (re-write) recharts.org to Angular for this but I'm not that great in core library stuff and didn't get further than just getting it to work.
comment in response to
post
I've contributed to a few Angular -specific open-source projects. May I join too? 🥹
comment in response to
post
Crosspost to dev.to for better reach + community, but I always recommend keeping a copy of your content on your own domain for SEO.
Also, dev.to supports listening to an RSS Feed, to automatically post new articles which you publish wherever.