Skip to content

Commit 99565e8

Browse files
corneliusyaovicorneliusyaovi
authored
Merge pull request #54 from ChijiokeFLW/master
Added progressive retry attempts to Flutterwave script download
2 parents 7f04840 + 7a7be04 commit 99565e8

17 files changed

+18077
-2929
lines changed

‎.babelrc.js

+1
Original file line numberDiff line numberDiff line change
@@ -10,4 +10,5 @@ module.exports = {
1010
],
1111
'@babel/preset-typescript',
1212
],
13+
1314
};

‎.github/ISSUE_TEMPLATE/bug_report.md

+45
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: bug
6+
assignees: ''
7+
8+
---
9+
10+
Have you read our [Code of Conduct](https://github.com/Flutterwave/React/blob/master/CONTRIBUTING.md)? By filing an Issue, you are expected to comply with it, including treating everyone with respect
11+
12+
Do you want to ask a question? Are you looking for support? The developer slack is the best place for getting [support](https://bit.ly/34Vkzcg)
13+
14+
### Description
15+
16+
<!-- Description of the issue -->
17+
18+
### Steps to Reproduce
19+
20+
1. <!-- First Step -->
21+
2. <!-- Second Step -->
22+
3. <!-- and so on… -->
23+
24+
**Expected behaviour:**
25+
26+
<!-- What you expect to happen -->
27+
28+
**Actual behaviour:**
29+
30+
<!-- What actually happens -->
31+
32+
**Reproduces how often:**
33+
34+
<!-- What percentage of the time does it reproduce? -->
35+
36+
### Configuration
37+
38+
- API Version: <!-- v2 or v3 -->
39+
- Environment: <!-- test mode or live mode -->
40+
- Browser: <!-- [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ] -->
41+
- Language: <!-- [all | Node X.X | TypeScript X.X | Python X.X | ES6/7 | ES5 | Dart | Android X.X | PHP X.X | Laravel X.X ] -->
42+
43+
### Additional Information
44+
45+
<!-- Any additional information, configuration or data that might be necessary to reproduce the issue e.g. detailed explanation, stack traces, related issues, suggestions on how to fix, links for us to have more context like StackOverflow, Gitter, etc. -->

‎.github/ISSUE_TEMPLATE/config.yml

+5
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: Developer Support Forum
4+
url: https://forum.flutterwave.com
5+
about: If you're having general trouble with your integration, Kindly contact our support team.

‎CONTRIBUTING.md

+83
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
# Community contribution guide
2+
3+
Thank you for taking the time to contribute to our library🙌🏾.
4+
5+
In this section, we detail everything you need to know about contributing to this library.
6+
7+
8+
9+
**[Code of Conduct](https://github.com/probot/template/blob/master/CODE_OF_CONDUCT.md)**
10+
11+
## **I don't want to contribute, I have a question**
12+
13+
Please don't raise an issue to ask a question. You can ask questions on our [forum](http://forum.flutterwave.com) or developer [slack](https://bit.ly/34Vkzcg). We have an army of Engineers on hand to answer your questions there.
14+
15+
## How can I contribute?
16+
17+
### Reporting a bug
18+
19+
Have you spotted a bug? Fantastic! Before raising an issue, here are some things to do:
20+
21+
1. Search to see if another user has reported the bug. For existing issues that are still open, add a comment instead of creating a new one.
22+
2. Check our forum and developer slack to confirm that we did not address it there.
23+
24+
When you report an issue, it is important to:
25+
26+
1. Explain the problem
27+
- Use a clear and descriptive title to help us to identify the problem.
28+
- Describe steps we can use to replicate the bug and be as precise as possible.
29+
- Include screenshots of the error messages.
30+
2. Include details about your configuration and setup
31+
- What version of the library are you using?
32+
- Did you experience the bug on test mode or live?
33+
- Do you have the recommended versions of the library dependencies?
34+
35+
> 💡 Please make use of the issue template when reporting bugs.
36+
37+
### Requesting a feature
38+
39+
If you need an additional feature added to the library, kindly send us an email at [email protected]. Be sure to include the following in your request:
40+
41+
1. A clear title that helps us to identify the requested feature.
42+
2. A brief description of the use case for that feature.
43+
3. Explain how this feature would be helpful to your integration.
44+
4. Library name and version.
45+
46+
### Submitting changes (PR)
47+
48+
Generally, you can make any of the following changes to the library:
49+
50+
1. Bug fixes
51+
2. Performance improvement
52+
3. Documentation update
53+
4. Functionality change (usually new features)
54+
55+
> 💡 Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of the library will generally not be accepted.
56+
57+
Follow these steps when making a pull request to the library:
58+
59+
1. Fork the repository and create your branch from master.
60+
2. For all types of changes (excluding documentation updates), add tests for the changes.
61+
3. If you are making a functionality change, update the docs to show how to use the new feature.
62+
4. Ensure all your tests pass.
63+
5. Make sure your code lints.
64+
6. Write clear log messages for your commits. one-liners are fine for small changes, but bigger changes should have a more descriptive commit message (see sample below).
65+
7. Use present tense for commit messages, "Add feature" not "Added feature”.
66+
8. Ensure that you fill out all sections of the PR template.
67+
9. Raise the PR against the `dev` branch.
68+
10. After you submit the PR, verify that all [status checks](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) are passing
69+
70+
```markdown
71+
$ git commit -m "A brief summary of the commit
72+
>
73+
> A paragraph describing what changed and its impact."
74+
```
75+
76+
> 💡 For your pull request to be reviewed, you need to meet the requirements above. We may ask you to complete additional tests, or other changes before your pull request can be ultimately accepted.
77+
78+
79+
We encourage you to contribute and help make the library better for the community. Got questions? send us a [message](https://bit.ly/34Vkzcg).
80+
81+
Thank you.
82+
83+
The Flutterwave team 🦋

‎LICENSE ‎LICENSE.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
MIT License
22

3-
Copyright (c) 2020 Joel Ugwumadu
3+
Copyright (c) 2020 Flutterwave
44

55
Permission is hereby granted, free of charge, to any person obtaining a copy
66
of this software and associated documentation files (the "Software"), to deal

0 commit comments

Comments
 (0)