Merge pull request #97 from razorpay/travis_test

Travis test - Added test environment.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,56 @@
+---
+name: "🐛 Bug Report"
+about: Report a reproducible bug or regression in Razorpay Flutter plugin.
+title: ''
+labels: 'Needs: Triage :mag:'
+
+---
+
+<!--
+------ 👆 Click "Preview"!
+
+HI! PLEASE STOP TO READ THIS!! IF YOU DO NOT FOLLOW THE INSTRUCTIONS, YOUR ISSUE
+WILL LIKELY BE CLOSED.
+
+* Please fill out this template with all the relevant information so we can understand what's going on and fix the issue. We appreciate bugs filed and PRs submitted!
+
+-->
+
+## Description
+
+Please provide a clear and concise description of what the bug is. Include screenshots if needed.
+Please test using the latest Razorpay pod release to make sure your issue has not already been fixed. 
+
+## Razorpay pod Version :
+
+Open `podfile` for checking the razorpay-pod version if it's not mentioned their then open `podfile.lock` and copy the pod version here. 
+
+## Xcode Version :
+Open Xcode > Go to `About Xcode` > copy the Xcode version here.
+
+### What you did:
+
+<!-- What you were doing -->
+
+### What happened:
+
+<!-- Please provide the full error message/screenshots/anything -->
+
+## Steps To Reproduce
+Provide a detailed list of steps that reproduce the issue.
+
+1.
+2.
+
+### Suggested solution:
+
+<!--
+It's ok if you don't have a suggested solution, but it really helps if you could
+do a little digging to come up with some suggestions on how to improve things.
+-->
+
+## Code example, screenshot, or link to a repository:
+Please provide a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
+You may provide a screenshot of the application if you think it is relevant to your bug report.
+Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve
+

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,9 @@
+blank_issues_enabled: false
+contact_links:
+    - name: ⤴️ Upgrade Issue or Installation issue
+      url: https://pub.dev/packages/razorpay_flutter
+      about: Need help upgrading to the latest flutter version? Follow steps from our plugin docuemntation.
+
+    - name: 🤔 Need some help in Integrations
+      url: https://razorpay.com/integrations/
+      about: Looking for help with your app? Please refer to the integration documentation.

.github/ISSUE_TEMPLATE/feature_Request.md

@@ -0,0 +1,43 @@
+---
+name: 💡 Feature Request
+about: I have a suggestion (and might want to implement myself 🙂)!
+---
+
+<!--
+
+Vote on feature requests by adding a 👍. This helps maintainers prioritize what
+to work on.
+
+* Please fill out this template with all the relevant information so we can
+  understand what's going on and fix the issue. We appreciate bugs filed and PRs
+  submitted!
+
+* Please make sure that you are familiar with and follow the Code of Conduct for
+  this project (found in the CODE_OF_CONDUCT.md file).
+
+-->
+
+### Describe the feature you'd like:
+
+<!--
+A clear and concise description of what you want to happen. Add any considered
+drawbacks.
+-->
+
+### Suggested implementation:
+
+<!-- Helpful but optional 😀 -->
+
+### Describe alternatives you've considered:
+
+<!--
+A clear and concise description of any alternative solutions or features you've
+considered.
+-->
+
+### Teachability, Documentation, Adoption, Migration Strategy:
+
+<!--
+If you can, explain how users will be able to use this and possibly write out a
+version of the docs.
+-->

.travis.yml

@@ -1,9 +1,12 @@
 # references:
 # * http://www.objc.io/issue-6/travis-ci.html
 # * https://github.com/supermarin/xcpretty#usage
+# * https://github.com/codecov/example-swift
+
+language:
+  - swift
 
-os: osx
 osx_image: xcode11.3
 
 script:
-  - xcodebuild test -project Example.xcworkspace -scheme Example -destination "platform=iOS Simulator,name=iPhone 11" CODE_SIGNING_REQUIRED=NO
+ xcodebuild -workspace Example.xcworkspace -scheme Example -sdk iphonesimulator ONLY_ACTIVE_ARCH=NO

CODE_OF_CONDUCT.md

@@ -0,0 +1,40 @@
+# Code of Conduct
+
+The Code of Conduct governs how we behave in public or in private
+whenever the project will be judged by our actions.
+We expect it to be honored by everyone who represents the project
+officially or informally,
+claims affiliation with the project,
+or participates directly.
+
+We strive to:
+
+* **Be open**: We invite anybody to participate in any aspect of our projects.
+  Our community is open, and any responsibility can be carried
+  by any contributor who demonstrates the required capacity and competence.
+* **Be empathetic**: We work together to resolve conflict,
+  assume good intentions,
+  and do our best to act in an empathic fashion.
+  By understanding that humanity drops a few packets in online interactions,
+  and adjusting accordingly,
+  we can create a comfortable environment for everyone to share their ideas.
+* **Be collaborative**: We prefer to work transparently
+  and to involve interested parties early on in the process.
+  Wherever possible, we work closely with others in the open source community
+  to coordinate our efforts.
+* **Be decisive**: We expect participants in the project to resolve disagreements constructively.
+  When they cannot, we escalate the matter to structures
+  with designated leaders to arbitrate and provide clarity and direction.
+* **Be responsible**: We hold ourselves accountable for our actions.
+  When we make mistakes, we take responsibility for them.
+  When we need help, we reach out to others.
+  When it comes time to move on from a project,
+  we take the proper steps to ensure that others can pick up where we left off.
+
+This code is not exhaustive or complete.
+It serves to distill our common understanding of a
+collaborative, shared environment and goals.
+We expect it to be followed in spirit as much as in the letter.
+
+---
+*Some of the ideas and wording for the statements above were based on work by   [Mozilla](https://wiki.mozilla.org/Code_of_Conduct/Draft), [Ubuntu](http://www.ubuntu.com/about/about-ubuntu/conduct), and [Twitter](https://github.com/twitter/code-of-conduct). We thank them for their work and contributions to the open source community.*

CONTRIBUTING.md

@@ -1,33 +1,9 @@
-# Contributing Code
+# Contributing Guidelines
 
-- Checkout the latest master to make sure the feature hasn't been implemented or
-the bug hasn't been fixed yet.
+* Fork the project.
+* Make your feature addition or bug fix.
+* Add tests for it. This is important so I don't break it in a future version unintentionally.
+* Commit just the modifications, do not mess with the CHANGELOG.md files.
+* Ensure your code is nicely formatted style.
+* Send the pull request.
 
-- Check the issue tracker to make sure someone already hasn't requested it and/or
-contributed to it.
-
-- Fork the repo.
-
-- We follow LLVM style code formatting. We use [`clang-format`](http://clang.llvm.org/docs/ClangFormat.html) to achieve this.
-
-    The easiest way to do this is using [`ClangFormat-Xcode`](https://github.com/travisjeffery/ClangFormat-Xcode) plugin by [Travis Jeffery](https://github.com/travisjeffery). Here are the steps to get you started with it.
-
-    - Install Homebrew. Find instructions [here](http://brew.sh/).
-    - Run the following on Terminal `brew install clang-format`.
-    - Install `Alcatraz` package manager for Xcode. Find instructions [here](http://alcatraz.io/).
-    - Start Xcode and find Alcatraz under Window > Package Manager (or simply press ⌘+9 key combination).
-    - Search for *ClangFormat* and install.
-    - Restart Xcode.
-
-    You'll find `Clang Format` under Edit in Xcode. Enable *Format on Save* and make sure you use *LLVM* configuration.
-
-- Make your change.
-
-- Push to your fork. Write a [good commit message][commit]. Submit a pull request.
-
-  [commit]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
-
-Others will give constructive feedback.
-This is a time for discussion and improvements,
-and making the necessary changes will be required before we can
-merge the contribution.