Files
sf-app-platform/apps/mobile_app/pubspec.yaml
aitorarana 5186c21e9a Merge branch 'customer-service' into legacy
# Conflicts:
#	apps/mobile_app/lib/navigation/app_router.dart
#	modules/legacy/melos_legacy.iml
#	packages/navigation/lib/app_routes.dart
#	packages/sf_localizations/assets/l10n/en.json
#	packages/sf_localizations/assets/l10n/es.json
#	packages/sf_localizations/lib/src/generated/i18n.dart
2026-02-13 09:34:45 +01:00

152 lines
5.2 KiB
YAML

name: sf_app_platform
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.9.2
# Dependencies specify other packages that your package needs in order to work.
# To automatically upgrade your package dependencies to the latest versions
# consider running `flutter pub upgrade --major-versions`. Alternatively,
# dependencies can be manually updated by changing the version numbers below to
# the latest version available on pub.dev. To see which dependencies have newer
# versions available, run `flutter pub outdated`.
dependencies:
flutter:
sdk: flutter
flutter_localizations:
sdk: flutter
flutter_riverpod: ^3.0.3
get_it: ^9.0.5
go_router: ^17.0.0
#modules dependencies go here
auth:
path: ../../modules/auth
home:
path: ../../modules/home
profile:
path: ../../modules/profile
notifications:
path: ../../modules/notifications
dashboard_shell:
path: ../../modules/dashboard_shell
legacy_dashboard_shell:
path: ../../modules/legacy/modules/legacy_dashboard_shell
hub:
path: ../../modules/legacy/modules/hub
customer_service:
path: ../../modules/legacy/modules/customer_service
splash:
path: ../../modules/splash
account:
path: ../../modules/legacy/modules/account
functions:
path: ../../modules/legacy/modules/functions
#packages dependencies go here
navigation:
path: ../../packages/navigation
design_system:
path: ../../packages/design_system
sf_localizations:
path: ../../packages/sf_localizations
fonts:
path: ../../packages/fonts
sf_infrastructure:
path: ../../packages/sf_infrastructure
utils:
path: ../../packages/utils
#dependencies go here
cupertino_icons: ^1.0.8
flutter_svg: ^2.2.1
go_router_builder: ^4.1.1
build_runner: ^2.7.1
flutter_dotenv: ^6.0.0
country_code_picker: ^3.4.1
flutter_native_splash: ^2.4.7
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 your
# package. See that file for information about deactivating specific lint
# rules and activating additional ones.
flutter_lints: ^5.0.0
flutter_launcher_icons: ^0.14.4
# 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:
- assets/images/ui/
- assets/images/logos/
- .env
# An image asset can refer to one or more resolution-specific "variants", see
# https://flutter.dev/to/resolution-aware-images
# For details regarding adding assets from package dependencies, see
# https://flutter.dev/to/asset-from-package
# 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/to/font-from-package
flutter_native_splash:
fullscreen: true
color: "#F7F7F7"
image: assets/images/logos/logo_splash.png
android_gravity: center
ios_content_mode: scaleAspectFit
android: true
ios: true
web: false
android_12:
color: "#F7F7F7"
icon_background_color: "#F7F7F7"
image: assets/images/logos/logo_splash.png