Ooh! That makes more sense
@ajitpanigrahi.com
Level 26 Mage / SDE3 @Fortinet ✦ Work: Frontend Infra & Tooling, A11y, Design, UX ✦ @ajitzero everywhere else npm packages for Angular: Animated Icons: https://www.npmjs.com/package/ng-animated-icons Auto Animate: www.npmjs.com/package/ng-auto-animate
Ooh! That makes more sense
Happy for the team!
Saw this on Twitter first, with the Kickstarter link upfront, and immediately thought it was an elaborate phishing attempt. Is this why Zach stopped using Twitter 😂
But please, just retain David Green.
awesome-possum-balloon-smile-sm is weird.
github.com/11ty/11ty-we...
One more suggestion: angularprimitives.com
I love this implementation of Analog as a docs site and have been referring to it multiple times for some things I wanted to reuse. Even had the same idea to make a blog template based on this, but couldn't make time for it
Looking at the code makes complete sense to me. This is a pretty neat pattern!
I'm not the most up to date on testing libs & utilities, so I thought somebody figured out a performant way to do this "magically" 😅
I used to hate magic, now we tolerate each other 😂
kinda off-topic: where does { heading } come from? Is it a magic variable that binds to all h1-h6 tags? Or maybe just the h1 tag?
This is not even a hot take.
It's crazy just how many clearly synchronous states were shoehorned into BehaviourSubject. Signal FTW!
Worse still: sometime last year, when our project was still on v14 w/o signals, a colleague added a ReplaySubject with the explanation of "ChatGPT suggested this." 🤦♂️
We tried vibe coding it was called dreamweaver
the wild part?
5 minutes with @astro.build and you can use it as a cross-document Pixelated View Transition 🤖
@view-transition {
navigation: auto;
}
then apply the demo code to the ::view-transition pseudo-elements 🚀
We have a few teams slowly rewriting Angular.js (v1) to v17 too 😂
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.
This is the first genuine TIL for me in years, and something that's actually a decent progressive enhancement!
www.stefanjudis.com/today-i-lear...
I just saw someone post about Indian Railways over on LinkedIn!
They (www.irctc.co.in) use Angular 9!
The new Web Weekly is out. 🍾
This time:
- When do forms submit on `ENTER` key press?
- Chrome's / Safari's tight mode
- `Object.groupBy`
- A massive CSS wishlist
- HTML-driven speculation rules
➕ As always: new tools, web platform news and some music!
Enjoy!
www.stefanjudis.com/blog/web-wee...
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.
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.
I believe we can enforce the type when using signal inputs. This type mismatch issue exists for all decorator-based properties
Just had a quick glance, but what makes this article specifically v19+? Is it because contentChild etc. are out of dev preview?
What was your use case to get to this point and discover this? A custom error message component?
So I was a guest at a meetup last week. One of the participants used an AI notes and summary tool.
The thing that struck me when looking at the summary afterwards is that what got talked about most was actually the least important part of the conversation, but the tool had no way of knowing that.
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
Congratulations Corbin!
Sure!
Screenshot of linked article where some links are breaking the layout when they are wider than the device width
These links should have break-word I think
*child, not cold
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
Payload was agnostic initially (and honestly still is) but is prioritising the Next.js integration more (for marketing, I assume)
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
What's the best place to pick up an SVG version of the Bluesky Icon @bsky.app for personal websites?
Framer Motion's core lib is now out as motion.dev (just "Motion")
Time to make the Angular port?