We recommend that anyone interested in contributing to this library use this sample app as part of their development workflow when introducing or testing changes.
- Gradle version: 7.0 or higher
- Android API level: 26 or higher
Each storage provider requires specific secrets for configuration. Please follow the individual storage provider configuration guides:
For using the plugins for development locally, there are two approaches:
In this scenario, you can use local modules (sub-projects) located inside the packages/ directory instead of relying on Maven Local dependencies. This setup allows you to modify the code in a plugin and see the changes instantly in the sample app without needing to publish to Maven Local.
To use local modules, add the following entry to your project's local.properties file:
useLocalProjects=trueAdditionally you can add it as a flag to your gradlew command:
./gradlew -P useLocalProjects=true ...To use Maven Local, add the following entry to your project's local.properties file:
useMavenLocal=trueAdditionally you can add it as a flag to your gradlew command:
./gradlew -P useMavenLocal=true ...When you make changes to any module within the packages/ directory, you need to publish the specific module to Maven Local to reflect those changes.
Before publishing other modules, you must publish the core module first by running the following command:
./gradlew :packages:core:publishToMavenLocalThis ensures that any dependencies on the core module are resolved correctly.
After publishing the core module, you can publish the remaining modules. You have two options:
- To publish all modules:
# From the root directory
./gradlew publishToMavenLocal- To publish a specific module:
./gradlew :packages:{module}:publishToMavenLocal- See LICENSE