Was thinking about using arrow or block functions. In the past I preferred arrow, but noticed that it makes code longer and less readable.
Compare. Which way do you prefer?
Compare. Which way do you prefer?
Sharing GraphQL lifehack
Here's how you can enable autocompletes for fields/fragments/queries:
1. Install graphql plugin (IntelliJ, VsCode)
2. Create
Enjoy autocompletes and analysis!
Here's how you can enable autocompletes for fields/fragments/queries:
1. Install graphql plugin (IntelliJ, VsCode)
2. Create
graphql.config.yml in the root:
schema:
- "schema.graphqls"
documents:
- "**/*.graphql"
Enjoy autocompletes and analysis!
JetBrains Marketplace
GraphQL - IntelliJ IDEs Plugin | Marketplace
Provides GraphQL language support to all JetBrains IDEs that support JavaScript. Features Schema-aware completion, error highlighting, and documentation Syntax...
Learn how scroll works in Flutter, the differences between scroll widgets, and how to build efficient layouts using slivers for best performance.
https://lazebny.io/flutter-slivers
#article #flutter #slivers
https://lazebny.io/flutter-slivers
#article #flutter #slivers
Michael Lazebny
Flutter Slivers: How Scrolling Works
Learn how scroll works in Flutter, the differences between scroll widgets, and how to build efficient layouts using slivers for best performance.
I created a simple but much more powerful alternative to Widgetbook, Storybook, and similar tools.
It automatically generates routes for GoRouter (supports deep links).
It also makes it very easy to create configurations, fields, etc., for customizing widgets.
This is just an example—it will be improved over time and might eventually be added to sizzle starter or a separate package.
Github Link
#flutter
It automatically generates routes for GoRouter (supports deep links).
It also makes it very easy to create configurations, fields, etc., for customizing widgets.
This is just an example—it will be improved over time and might eventually be added to sizzle starter or a separate package.
Github Link
#flutter
Rust is an amazing language for FFI in Dart
All you need to do is define the extern C function, run cbindgen to generate a C header file, and then run ffigen, which generates safe Dart bindings.
Here is how I implemented upscale using Rust's "image" crate, which is 50x faster than dart's "image" package.
I think this is not the best solution and if you know how to improve it, it would be greatly appreciated! :)
#dart #rust #ffi
All you need to do is define the extern C function, run cbindgen to generate a C header file, and then run ffigen, which generates safe Dart bindings.
Here is how I implemented upscale using Rust's "image" crate, which is 50x faster than dart's "image" package.
I think this is not the best solution and if you know how to improve it, it would be greatly appreciated! :)
#dart #rust #ffi
Learn how to use the @Deprecated annotation to migrate Dart code incrementally
https://lazebny.io/deprecated-in-dart/
https://lazebny.io/deprecated-in-dart/
Michael Lazebny
How to use @Deprecated in Dart
Learn how to use Dart's @Deprecated annotation to safely refactor code and manage CI deprecation warnings effectively.
This media is not supported in your browser
VIEW IN TELEGRAM
Created a minimal example of custom AppBars using SliverPersistentHeaderDelegate.Take a look here https://github.com/hawkkiller/pageheader/blob/main/lib/page_header.dart
#flutter #flutterdev
#flutter #flutterdev
You can pin the toolbar to the top of your vscode window.
https://x.com/TahaTesser/status/1917094263000584605
https://x.com/TahaTesser/status/1917094263000584605
The next article will be about building efficient CI pipelines for large flutter projects
Happy to share that Sizzle Starter is now updated to Flutter 3.32.0
Together with this update, I have landed a few important ones:
- Now app (root) project is located in "app" folder. This stimulates modularization principles
- flutter gen-l10n is not used anymore for localizations in favor of intl_utils (from Localizely)
- some other minor changes..
https://github.com/hawkkiller/sizzle_starter
Together with this update, I have landed a few important ones:
- Now app (root) project is located in "app" folder. This stimulates modularization principles
- flutter gen-l10n is not used anymore for localizations in favor of intl_utils (from Localizely)
- some other minor changes..
https://github.com/hawkkiller/sizzle_starter
GitHub
GitHub - hawkkiller/sizzle_starter: Production ready template for flutter applications.
Production ready template for flutter applications. - hawkkiller/sizzle_starter
Mobile Tech
Happy to share that Sizzle Starter is now updated to Flutter 3.32.0 Together with this update, I have landed a few important ones: - Now app (root) project is located in "app" folder. This stimulates modularization principles - flutter gen-l10n is not used…
Following updates might be focused on modularization practices, such as moving features to feature-modules and shared code into corresponding packages, so they are more reusable.
If you want to make your VS Code indentation a bit more beautiful for #Flutter widgets, set "dart.previewFlutterUiGuides" to true
If I'm not mistaken, the same thing exists in IDEA :)
If I'm not mistaken, the same thing exists in IDEA :)