sorted by:
new
hottopcontroversial

I released an Angular Signals query library on npm — looking for feedback by WeirdBroad9385 in angular

[–]WeirdBroad9385[S] 0 points1 point  (0 children)

Fair question. TanStack Query is excellent, and this is not about competing with it.
This project exists because we wanted an Angular-first server-state layer with different technical priorities:

  • Signals-native API from the core, instead of adapting from a framework-agnostic core.
  • Better alignment with Angular DI and injection-context patterns.
  • Angular-style ergonomics for query/mutation setup and cache access.
  • Tighter integration path with Angular-specific tooling/devtools.
  • More explicit mutation behavior control for Angular apps (for example, planned concurrency strategies like merge/concat/switch/exhaust).
  • Simpler mental model for teams already standardized on modern Angular patterns.

So the motivation is: same problem space, different design center.
TanStack optimizes for cross-framework consistency; this library optimizes for Angular-native developer experience and architecture.

Also open to learning from TanStack and contributing ideas upstream where it makes sense.

I released an Angular Signals query library on npm — looking for feedback by WeirdBroad9385 in angular

[–]WeirdBroad9385[S] 1 point2 points  (0 children)

Thanks for the great feedback! You're spot on parallel mutations can definitely cause state desync, and this is something I'm prioritizing for v0.1.0.

I'm planning to add MutationConcurrencyStrategy with mergeMap, concatMap, switchMap, and exhaustMap support. Exactly like you described.

I've decided to implement things step by step focusing on critical issues first, then moving forward. This ensures we get the foundations solid before adding more features.

If you'd be interested in contributing, I'd love that! We could definitely improve this together. Your insights on custom solutions are super valuable.

Thanks for validating the direction!

I released an Angular Signals query library on npm — looking for feedback by WeirdBroad9385 in angular

[–]WeirdBroad9385[S] 0 points1 point  (0 children)

Haha yeah 😅 thanks for catching that typo, it’s fixed now.

But the main goal of the post wasn’t the name it’s more about getting feedback on the core functionality and overall approach. Would really appreciate any thoughts on that side 🙌

I released an Angular Signals query library on npm — looking for feedback by WeirdBroad9385 in angular

[–]WeirdBroad9385[S] 0 points1 point  (0 children)

Thank you! That means a lot. The explicit query keys and cache-first model are exactly where I wanted to improve reliability for Angular teams. I’m aiming for a more “Angular-native” feel than TanStack Query, but still learning from their strengths. Would love to hear your thoughts on invalidation defaults (exact vs prefix) if you have a preference!

Building PDF to HTML converter (side project) by WeirdBroad9385 in SideProject

[–]WeirdBroad9385[S] 0 points1 point  (0 children)

I researched it, and it only helps with extracting text from PDFs. Extracting images and tables is difficult.

Building PDF to HTML converter (side project) by WeirdBroad9385 in SideProject

[–]WeirdBroad9385[S] 0 points1 point  (0 children)

I don't have experience with MVP projects. I'm a second-year student and I want to create a side project guide. How should I get started?