epos_frontend_shared 1.5.14 copy "epos_frontend_shared: ^1.5.14" to clipboard
epos_frontend_shared: ^1.5.14 copied to clipboard

A flutter package project.

Flutter component library which can be shared across different projects and clients we have this package to create a common component shared library where we can put the reusable components and use them as a library in different projects.

This is the dev pub package here https://pub.flutter-io.cn/packages/epos_frontend_shared

How to use this package #

  1. Add the package to your pubspec.yaml file
dependencies:
  epos_frontend_shared: latest_version
  1. Import the package in your Dart file
import 'package:epos_frontend_shared/epos_frontend_shared.dart';
  1. Use the components in your Flutter app

How to publish the package #

  1. Update the version number in pubspec.yaml
version: 1.0.0+1
  1. Update the CHANGELOG.md file with the new version number and a description of the changes
  2. Run the following command to publish the package
flutter pub publish
4. Follow the prompts to confirm the publication
5. Once the package is published, it will be available on pub.flutter-io.cn and can be used in other Flutter projects

How to contribute #

  1. Fork the repository
  2. Create a new branch for your feature or bug fix
  3. Make your changes and commit them with a descriptive message
  4. Push your changes to your forked repository
  5. Create a pull request to the main repository
  6. Wait for the pull request to be reviewed and merged
  7. Once the pull request is merged, your changes will be included in the next release of the package
  8. If you have any questions or need help, feel free to open an issue in the repository
  9. We welcome contributions from everyone, so feel free to suggest new features or improvements
  10. Please make sure to follow the code style and conventions used in the project
  11. If you are adding new features, please include tests to ensure the functionality works as expected
  12. If you are fixing a bug, please include a test that reproduces the issue and verifies the fix
  13. If you are updating documentation, please make sure to keep it clear and concise
  14. If you are adding new dependencies, please make sure to check if they are necessary and if there are any alternatives