We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The code generated by slidy is completely different from that presented in the documentation.
https://triple.flutterando.com.br/docs/intro/getting-started
https://triple.flutterando.com.br/docs/intro/getting-started#import
"" name: pareto description: "A new Flutter project."
flutter pub publish
publish_to: 'none' # Remove this line if you wish to publish to pub.dev
version: 1.0.0+1
environment: sdk: '>=3.2.0 <4.0.0'
dependencies: flutter: sdk: flutter
cupertino_icons: ^1.0.2 flutter_triple: ^3.0.0 flutter_modular: any
dev_dependencies: flutter_test: sdk: flutter
analysis_options.yaml
flutter_lints: ^2.0.0 triple_test: ^2.0.0 modular_test: any
flutter:
uses-material-design: true
""
As there are divergences between the documentation, it is difficult to know which one will be correct, which takes time to develop.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The code generated by slidy is completely different from that presented in the documentation.
https://triple.flutterando.com.br/docs/intro/getting-started
https://triple.flutterando.com.br/docs/intro/getting-started#import
""
name: pareto
description: "A new Flutter project."
The following line prevents the package from being accidentally published to
pub.dev using
flutter pub publish
. This is preferred for private packages.publish_to: 'none' # Remove this line if you wish to publish to pub.dev
The following defines the version and build number for your application.
A version number is three numbers separated by dots, like 1.2.43
followed by an optional build number separated by a +.
Both the version and the builder number may be overridden in flutter
build by specifying --build-name and --build-number, respectively.
In Android, build-name is used as versionName while build-number used as versionCode.
Read more about Android versioning at https://developer.android.com/studio/publish/versioning
In iOS, build-name is used as CFBundleShortVersionString while build-number is used as CFBundleVersion.
Read more about iOS versioning at
https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
In Windows, build-name is used as the major, minor, and patch parts
of the product and file versions while build-number is used as the build suffix.
version: 1.0.0+1
environment:
sdk: '>=3.2.0 <4.0.0'
dependencies:
flutter:
sdk: flutter
cupertino_icons: ^1.0.2
flutter_triple: ^3.0.0
flutter_modular: any
dev_dependencies:
flutter_test:
sdk: flutter
The "flutter_lints" package below contains a set of recommended lints to
encourage good coding practices. The lint set provided by the package is
activated in the
analysis_options.yaml
file located at the root of yourpackage. See that file for information about deactivating specific lint
rules and activating additional ones.
flutter_lints: ^2.0.0
triple_test: ^2.0.0
modular_test: any
For information on the generic Dart part of this file, see the
following page: https://dart.dev/tools/pub/pubspec
The following section is specific to Flutter packages.
flutter:
The following line ensures that the Material Icons font is
included with your application, so that you can use the icons in
the material Icons class.
uses-material-design: true
To add assets to your application, add an assets section, like this:
assets:
- images/a_dot_burr.jpeg
- images/a_dot_ham.jpeg
An image asset can refer to one or more resolution-specific "variants", see
https://flutter.dev/assets-and-images/#resolution-aware
For details regarding adding assets from package dependencies, see
https://flutter.dev/assets-and-images/#from-packages
To add custom fonts to your application, add a fonts section here,
in this "flutter" section. Each entry in this list should have a
"family" key with the font family name, and a "fonts" key with a
list giving the asset and other descriptors for the font. For
example:
fonts:
- family: Schyler
fonts:
- asset: fonts/Schyler-Regular.ttf
- asset: fonts/Schyler-Italic.ttf
style: italic
- family: Trajan Pro
fonts:
- asset: fonts/TrajanPro.ttf
- asset: fonts/TrajanPro_Bold.ttf
weight: 700
For details regarding fonts from package dependencies,
see https://flutter.dev/custom-fonts/#from-packages
""
As there are divergences between the documentation, it is difficult to know which one will be correct, which takes time to develop.
The text was updated successfully, but these errors were encountered: