floppypaste
@floppypaste.bsky.social
Flutter Developer. Check out my logging package: notice
Do you mean this one: github.com/dart-lang/la... Is there a place we can track the progress? I'm just very excited right now and want to know how long it'll be.
Augmentations · Issue #4154 · dart-lang/language
Tracking issue, see feature spec here https://github.com/dart-lang/language/blob/main/working/augmentation-libraries/feature-specification.md
github.com
September 14, 2025 at 5:59 PM
Do you mean this one: github.com/dart-lang/la... Is there a place we can track the progress? I'm just very excited right now and want to know how long it'll be.
I can't comprehend why the chose to name them this way. main-axis- / cross-axis-alignment would've simply done the job ...
March 13, 2025 at 1:30 PM
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.
March 6, 2025 at 10:25 AM
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
January 30, 2025 at 12:55 PM
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?
January 30, 2025 at 12:07 PM
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
January 29, 2025 at 11:43 PM
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
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
December 18, 2024 at 4:42 PM
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? 👉👈
December 18, 2024 at 7:45 AM
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
December 15, 2024 at 1:02 PM
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 🎉
December 15, 2024 at 1:02 PM
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? 😅
December 14, 2024 at 11:54 PM
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
December 14, 2024 at 11:54 PM
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?
December 14, 2024 at 11:46 PM
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?
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...
December 7, 2024 at 3:27 PM
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
December 3, 2024 at 5:03 PM
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
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.
November 29, 2024 at 3:46 PM
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.
November 25, 2024 at 3:57 PM
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.
Thanks, will definitely take a look!
November 21, 2024 at 8:38 PM
Thanks, will definitely take a look!
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!
November 21, 2024 at 6:02 PM
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!