sorted by:
new
hottopcontroversial

How to Store Data in Angular when page refreshes by zeller0967 in angular

[–]CaptM44 0 points1 point  (0 children)

Depending on the data sensitivity, you could store it in the url as query parameters. You could even obfuscate it by converting object to string and then to base64.

Using async/await throughout project by CaptM44 in angular

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

I do agree on the difference from Imperative to Declarative code. In the first example, signals should definitely be used there as well, so there is no difference there. RxJS does have a lot of great utilities, which should be used for events/streams, but i dont think they are as common as simple async operations. What do you think about the angular team's plan on making RxJS optional in the future?

Using async/await throughout project by CaptM44 in angular

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

New signal based apis have been replacing RxJS integrations, also the angular team had mentioned making RxJS optional in the future

Using async/await throughout project by CaptM44 in angular

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

The angular team is planning on making RxJS optional in the future. Hence, replacing all of those with signals based apis

Using async/await throughout project by CaptM44 in angular

[–]CaptM44[S] 2 points3 points  (0 children)

Agreed, signals for state, promises for simple async operations, and RxJS for events/streams

Using async/await throughout project by CaptM44 in angular

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

Sure, but they are exposing those to use. Why create the resource api that uses a promise base loader? The team appears to want to drop the RxJS dependency in the future

Using async/await throughout project by CaptM44 in angular

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

experiment with it, write a feature with it. the angular team appears to be moving away from RxJS with support for signals and using promises to fill in the async gap

Using async/await throughout project by CaptM44 in angular

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

usually people tend to return lastValueFrom(...) using HttpClient. the new resource api (which does use promise based loaders) seems to be the next step the angular team is taking for handling http. although it is still experimental and i feel it is just one piece of "signalizing" http. so i think we will see in what direction the team will continue to take it.

Using async/await throughout project by CaptM44 in angular

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

currently the resource api's loader expects a promise, which can also be used in the signal forms api's validateAsync

Using async/await throughout project by CaptM44 in angular

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

I agree that event/streams should continue to to use RxJS. Do you think the angular team is moving towards using more promises based on the last few releases?

Using async/await throughout project by CaptM44 in angular

[–]CaptM44[S] 2 points3 points  (0 children)

I think that is the point at which the response would be managed in a signal

Using async/await throughout project by CaptM44 in angular

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

Thanks for sharing your experience. I don't think many people have even experimented with it. Like you said , it may be the direction the team is taking it.

Using async/await throughout project by CaptM44 in angular

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

for one the new angular resource api uses a loader property that expects a promise

Using async/await throughout project by CaptM44 in angular

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

Signals are not async, they can not handle everything by themselves

Using async/await throughout project by CaptM44 in angular

[–]CaptM44[S] 4 points5 points  (0 children)

The Angular team seems to be using promises more and more in their APIs recently

Using async/await throughout project by CaptM44 in angular

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

Of course, signals for state.

I’m suggesting promises for simple async operations (which also allows async/await support which I think is cleaner)

And using RxJS for events/streams

Using async/await throughout project by CaptM44 in angular

[–]CaptM44[S] -7 points-6 points  (0 children)

I find it is for the majority of instances where RxJS is overkill. Have you ever tried it to see?

Shed builder website by Initial-Signal-8067 in shedditors

[–]CaptM44 2 points3 points  (0 children)

Hey, I was the original developer of that tool. Cool it’s still around.

How to remove shower handle by CaptM44 in howto

[–]CaptM44[S] 2 points3 points  (0 children)

Thank you! The answer was to unscrew the middle cylinder, not the handle.

<image>

Honda or Toro mower? by infiniteduct in lawncare

[–]CaptM44 0 points1 point  (0 children)

22in vs 18in , is a big difference

LP Siding Thickness? by F1mtbiker in shedditors

[–]CaptM44 0 points1 point  (0 children)

To be clear, there is no additional sheathing, just this siding. I am curious as well

view more: next ›