floppypaste

I can't comprehend why the chose to name them this way. main-axis- / cross-axis-alignment would've simply done the job ...

Are you planning on making it work with sliver layouts? With that feature, the package would be a clear no-brainer. Sadly a lot of my apps make extensive use of Slivers.

I was referring to the boilerplate required for json (or other formats) serialization that is written automatically by build_runner or macros. I'm interested if Ada simply requires you to write that manually like C does or if there is an alternative

Does Ada offer an alternative to writing all that boilerplate then?

I hope this is the right path for the future. Macros felt like the most fitting, natural step forward for the whole ecosystem, especially regarding the current pain points. build_runner was always a pain to use in the past (at least for my personal experience), so doubling down on it seems a bit odd

We have unfortunately decided to stop working on macros.

You can read the statement here: medium.com/dartlang/an-...

Feel free to ask me any follow up questions.

This is so awesome, this was a missing peace of flutter! How do you overlay the transitioning widgets and get their positions? Feels like magic not having to use a Host Widget somewhere

Could you add me too? 👉👈

I feel like the momentum for signals is framework-independently really really high but contrary to that, there aren't any resourcess right now that go more in-depth on the topic. I am missing guides on where to use them in your application (presentation-only vs signals-all-the-way) for example

Tha sounds great! So in general using signal containers to keep track of your resources (id -> model) in a reactive way is an expected use-case for signals? 😅 Looking forward to the container update 🎉

Maybe i am trying to hard to use signals as a caching framework? 😅

Could there be room for a hybrid approach? Staying completely sync for sync signals and using zoned values for computedAsync? Maybe my application is special, but i do a lot of async stuff like this with multiple dependencies and this one thing would really hold me back from migrating from Riverpod

The problem in my case is, that the dependency is part of a signal container and the result of a future is the key. I guess there is nothing I can really do in that case right?

Zones Manage your asynchronous code: handle uncaught errors, override behavior (such as printing and scheduling tasks), and more.

@rodydavis.com I was running into problems needing to use signals across async gaps yesterday. I was just wondering if you've ever considered using darts runZoned() for storing the evalContext across async gaps? dart.dev/libraries/as... Has most likely a performance impact, could still be worth it.

Do you mean the thing where the analyzer acts like the macro does not exist? I did discover a nice little workaround: bsky.app/profile/flop...

I've been experimenting with signals for the last few days and they are really amazing. Are you planning on adding linkedSignal() from angular too? Feels like a missing piece. I am not a friend of the whole import decides which signal you get thing, but i guess its just preference

Yessss 🎉🎉

Definitely data classes and json serialization for me. The dx of the build runner is horrible and so is the alternative of writing all that boilerplate by yourself. Other than that I am currently not very happy with the routing options available.

OMG I feel so stupid right now. I did some crazy over engineered shenanigans to make a 0 to "auto" transition (did some offstage stuff to get the wanted size of the animated widget) and even offered it as a library.

I absolutly despise #dart 's build runner dx although I couldn't live without it. The fact that i need to flood my codebase with tons of .g files generated in a 2-minute process every time i change a simple variable drives me actually a bit crazy. I desperately need macros.

Thanks, will definitely take a look!

What are some nice recent in-depth #dart and #flutter talks one shouldn't miss out on? I feel like the broader topics get a lot of attention while the deep dives fly unter the radar

It is also very common that some straight up rip their articles from sources like stack overflow. And some posts are just very emotional opinions presented as facts without any reasoning ... The good articles are behind a paywall though!

Macro doesn't execute when defined in a project outside of analysis roots · Issue #55670 · dart-lang/sdk I was investigating an issue @mit-mit / @davidmorgan are seeing of macros not executing in VS Code. I can reproduce the issue and it seems to be that when the project that contains a macros definit...

While this is really nice and works like a charm (The data_class package is awesome!) you need to keep in mind that breaking changes to the macro api are expected and this is not intended by the dart team afaict: github.com/dart-lang/sd.... Sill nice if you want to try it out though :)

A macro class extending another macro class without defining any fields. This makes the inheriting class be accepted as a macro by darts analyzer.

You can make the analyzer accept third-party macros by simply extending them in your project like so

You can't really use third-party macros with #flutter or #dart right now, because the analyzer currently only supports your own declared macros. I've discovered a very simple trick to make the analyzer happy though:

Get B if you can. You may want to use docker at some point, and it is a RAM hog on macOS

Jusant :)