Skip to content

altive/altfire

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

95 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Development

Release procedures for a altfire package.

  1. Create a branch for release.
  2. Run the melos version command.
  3. Run the git push origin release --follow-tags command. Push the changes and the created tags.
  4. Create a pull request for the pushed branch.
  5. Merge the pull request after review.
  6. Run the melos publish command on the main branch.
# Narrow down the target package as needed.
melos version --scope=altfire_tracker

# Specify the version manually, if necessary.
melos version \
--manual-version altfire_authenticator:0.1.6 \
--manual-version altfire_configurator:0.1.4 \
--manual-version altfire_messenger:0.2.1 \
--manual-version altfire_tracker:0.1.5 \

Add new example package

flutter create -e \
--org jp.co.altive \
--project-name ${PACKAGE_NAME}_example \
packages/${PACKAGE_NAME}/example

Add dependencies to example package

flutter pub add firebase_core \
'${PACKAGE_NAME}:{"path":"../"}' \
dev:altive_lints 

Configure FlutterFire

cd packages/${PACKAGE_NAME}/example
flutterfire configure

https://console.firebase.google.com/project/flutterfire-adapter

Update analysis_options.yaml

include: package:altive_lints/altive_lints.yaml
analyzer:
  exclude:
    - "lib/firebase_options.dart"