You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// use injection to see direct dependencies in each method
public Task<IActionResult> Get([FromServices]ITagsService service) =>
service
.GetAllAsync()
.Ok(tags => new { tags = tags});
// service
// .GetAllAsync()
// .Next(tags =>Ok(new { tags = tags}));
So to speak it is possible to avoid await keyword(and still be async) in most cases and use pipelining. Looks like F#.
The text was updated successfully, but these errors were encountered:
As much as I like this approach, I think it's just going too far. I was kind of trying to find the balance between the standard (already familiar to most) and functional way of doing things. Sadly(?), C# is not a functional language, so I think it's better we stick to the "basics" where there's no obvious benefit of doing it functionally.
What do you think about replacing things like:
to (whatever works)
So to speak it is possible to avoid
await
keyword(and still be async) in most cases and use pipelining. Looks like F#.The text was updated successfully, but these errors were encountered: