You can help Azure Communication UI Library with any of the following:
- Reporting and fixing issues
- Suggesting new features
- Increasing unit test coverage
- Answering any open issues
- Improving documentation
- Reviewing pull requests
We enthusiastically welcome contributions and feedback. You can fork the repo and start contributing now.
Here are the steps to start and develop inside iOS Mobile UI Library repo.
- Begin by cloning the Repo in your local environment,
cd
to theAzureCommunicationUI
folder in the root of the project directory. - Run
pod install
, this generates a.xcworkspace
file. - Open
AzureCommunicationUI.xcworkspace
file generated in the above step. - Hit
⌘+R
to start running.
For details on development guidelines and instructions on how to build and run the samples, visit the Demo App.
You can send pull requests to fix the open issues. For any pull request, it's recommended to open an issue and reach an agreement on an implementation design/plan with other contributors first.
We recommend making small and simple pull requests. Avoid making the implementation complicated when there is a simple, small alternative.
Please fork the repository and submit pull requests to develop
branch. For details on how to set up a fork of this repository and keep it up-to-date see Fork a Repo - GitHub Help.
When submitting a pull request, please add relevant tests and ensure your changes don't break any existing tests. Pull requests should be thoroughly tested and CI checks passed.
- Open the
AzureCommunicationUI.xcworkspace
with Xcode - Select
AzureCommunicationUICalling
orAzureCommunicationUIChat
scheme and target at any iOS simulator - Navigate to
Product
->Test
or hit⌘+U
to start testing
Please follow Before running the sample for the first time to have the EnvConfig.xcconfig
in your project directory with necessary values for Calling or Chat.
- Open the
AzureCommunicationUI.xcworkspace
with Xcode - Select
AzureCommunicationUIDemoApp
scheme and target at any iOS simulator/device - Navigate to
Product
->Test
or hit⌘+U
to start testing
Azure Mobile UI Library employs a few practices to ensure the clean code and project standards. Please follow these practices to make your Pull Request consistent with the MobileUILibrary
- SwiftLint is added to enforce coding style and conventions
- Swift API Design Guidelines is the guidelines we are following
- Microsoft Swift Style Guide is also what we adhere to
Once your PR is merged, your changes are ready to be published in a new version! We do manual publishes of new package versions semi-regularly.