Skip to content

Commit acfb76f

Browse files
pranshuchittorapranshuchittora
committed
feat: Initial version of RNEU
0 parents  commit acfb76f

23 files changed

+9404
-0
lines changed

‎.editorconfig

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
root = true
2+
3+
[*]
4+
end_of_line = lf
5+
insert_final_newline = true
6+
charset = utf-8
7+
indent_style = space
8+
indent_size = 2

‎.eslintignore

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
website
2+
coverage
3+
dist

‎.eslintrc

+7
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
{
2+
"extends": "@react-native-community",
3+
"rules": {
4+
"react-native/no-inline-styles": 0,
5+
"@typescript-eslint/no-unused-vars": ["error", { "ignoreRestSiblings": true }]
6+
}
7+
}

‎.github/CONTRIBUTING.MD

+42
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
# Contributing
2+
3+
Thanks for taking the time to checkout this repo and be willing to contribute!
4+
5+
If you have found an issue or would like to request a new feature, simply create a new issue. New issues come with a issue template, so make sure to fill out as much information as possible.
6+
7+
We also welcome pull requests, bug fixes and improved test coverage as contributions!
8+
9+
If this is your first open source contribution, please take a look at [this](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github) guide.
10+
11+
## Reporting Bugs & Feature Requests
12+
13+
If you would like to submit a feature request or report a bug, we encourage you to first look through the [issues](https://github.com/react-native-elements/react-native-elements/issues) and [pull requests](https://github.com/react-native-elements/react-native-elements/pulls) before filing a new issue.
14+
15+
Check out the [react-native-elements-app](https://github.com/react-native-elements/react-native-elements-app) repository to see how React Native Elements is used to build the [React Native Elements App](https://expo.io/@flyingcircle/projects/react-native-elements-app) on Expo.
16+
17+
## Submitting a Pull Request
18+
19+
If you wish to submit a pull request for a new feature or issue, you should start by forking this repository first. This should get you setup on your local machine:
20+
21+
### Setup
22+
23+
- Install [Node.js](https://nodejs.org/) and [yarn](https://yarnpkg.com) if you have not already. (_We suggest you to use node v6.x.x_)
24+
- Fork the **react-native-elements** repo [here](https://github.com/react-native-elements/react-native-elements)
25+
- `git clone <your-forked-repo-url> && cd react-native-elements`
26+
- `yarn install`
27+
- `yarn test`
28+
29+
Now create a new branch with a name that loosely describes the issue on which you will be working. Once you think you have addressed the issue in question, submit a pull request to the `next` branch.
30+
31+
### Committing and Pushing Changes
32+
33+
We like to provide informative and useful commit messages when pushing changes to the repo. This helps tremendously when sifting through the commit history to find a particular changeset. A useful guide for creating meaningful commit messages can be found [here.](https://github.com/conventional-changelog-archived-repos/conventional-changelog-angular/blob/ed32559941719a130bb0327f886d6a32a8cbc2ba/convention.md)
34+
35+
### Branching Strategy
36+
37+
There are 3 main branches:
38+
- `master` is the branch with the most recent deployed version
39+
- `next` is the main development branch. For new features and enhancements, base the
40+
changes off this branch.
41+
- `patch` is a branch for working on patch releases. If you have a bug fix
42+
that requires a fast release, use this branch.

‎.github/FUNDING.yml

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
open_collective: react-native-elements

‎.github/ISSUE_TEMPLATE/bug_report.md

+52
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
---
5+
6+
<!--
7+
Before filling out an issue:
8+
1. A bug means that there is something broken or outside expectations in react-native-elements. If you only need help writing your own components, check out the [Slack channel](https://react-native-elements-slack.herokuapp.com/) FIRST.
9+
2. If any section is left blank, there is a high possibility that the ticket will be closed. If you want your issue to get solved, you need to fill out ALL of the below fields. Otherwise, the ticket will likely be closed as not providing enough info.
10+
-->
11+
12+
**Explain what you did (Required)**
13+
14+
<!-- What you were trying to accomplish. -->
15+
16+
**Expected behavior (Required)**
17+
18+
<!-- A clear and concise description of what you expected to happen. -->
19+
20+
**Describe the bug (Required)**
21+
22+
<!-- A clear and concise description of what the bug is. -->
23+
24+
**To Reproduce (Required)**
25+
26+
We highly recommend that you re-create the bug on [Snack](https://snack.expo.io). If not, list the steps that a reviewer can take to reproduce the behaviour:
27+
28+
<!--
29+
Example:
30+
31+
```bash
32+
# Snack
33+
https://snack.expo.io/xxx
34+
35+
# Steps
36+
1. Go to '...'
37+
2. Click on '....'
38+
3. Scroll down to '....'
39+
4. See error
40+
```
41+
-->
42+
43+
**Screenshots (Required)**
44+
45+
<!-- If applicable, add screenshots to help explain your problem. -->
46+
47+
**Your Environment (Required):**
48+
49+
| software | version |
50+
| --------------------- | ------- |
51+
| react-native-elements | |
52+
| react-native | |

‎.github/ISSUE_TEMPLATE/feature-request.md

+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature Request
3+
about: Suggest an idea or enhancement for this project
4+
---
5+
6+
**Is your feature request related to a problem? Please Describe.**
7+
8+
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
9+
10+
**Describe the solution you'd like**
11+
12+
<!-- A clear and concise description of what you want to happen. -->
13+
14+
**Describe alternatives you've considered**
15+
16+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
17+
18+
**Additional context**
19+
20+
<!-- Add any other context or screenshots about the feature request here. -->

‎.github/PULL_REQUEST_TEMPLATE.md

+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
<!-- Thanks for submitting a pull request! Please provide enough information so that others can review your pull request. -->
2+
3+
**What kind of change does this PR introduce?**
4+
5+
<!-- E.g. a bugfix, feature, refactoring, build related change, etc… -->
6+
7+
**Did you add tests for your changes?**
8+
9+
**If relevant, did you update the documentation?**
10+
11+
**Summary**
12+
13+
<!-- Explain the **motivation** for making this change. What existing problem does the pull request solve? -->
14+
<!-- Try to link to an open issue for more information. -->
15+
16+
**Does this PR introduce a breaking change?**
17+
18+
<!-- If this PR introduces a breaking change, please describe the impact and a migration path for existing applications. -->
19+
20+
**Other information**

‎.github/workflows/build-and-deploy-to-dist.yml

+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
name: Build and Deploy next to dist
2+
on:
3+
push:
4+
branches:
5+
- next
6+
jobs:
7+
build:
8+
runs-on: ubuntu-latest
9+
steps:
10+
- uses: actions/checkout@v2
11+
with:
12+
persist-credentials: false # otherwise, the token used is the GITHUB_TOKEN, instead of your personal token
13+
fetch-depth: 0 # otherwise, you will failed to push refs to dest repo
14+
- name: Setup Node.js Env
15+
uses: actions/setup-node@v2
16+
with:
17+
node-version: '12'
18+
- name: Install and Build 🔧 # This example project is built using npm and outputs the result to the 'build' folder. Replace with the commands required to build your project, or remove this step entirely if your site is pre-built.
19+
run: |
20+
yarn
21+
yarn build
22+
- name: Create local changes
23+
run: |
24+
sed -i -e '/dist/d' .gitignore
25+
git add .
26+
- name: Commit files
27+
run: |
28+
git config --local user.email "41898282+github-actions[bot]@users.noreply.github.com"
29+
git config --local user.name "github-actions[bot]"
30+
git commit -m "New build" -a
31+
- name: Push changes
32+
uses: ad-m/github-push-action@master
33+
with:
34+
github_token: ${{ secrets.GITHUB_TOKEN }}
35+
branch: dist
36+
force: true

‎.gitignore

+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
node_modules
2+
.DS_Store
3+
*.log
4+
site
5+
coverage
6+
jsconfig.json
7+
.vscode/
8+
.idea/
9+
website/build
10+
.idea/
11+
package-lock.json
12+
build
13+
*.orig
14+
dist/

‎.prettierrc

+5
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
{
2+
"singleQuote": true,
3+
"trailingComma": "es5",
4+
"endOfLine": "auto"
5+
}

‎.travis.yml

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
language: node_js
2+
node_js:
3+
- 'stable'
4+
cache:
5+
yarn: true
6+
directories:
7+
- node_modules
8+
- website/node_modules
9+
branches:
10+
only:
11+
- master
12+
- next
13+
- patch
14+
install:
15+
- yarn global add codecov
16+
- yarn
17+
script:
18+
- yarn lint
19+
- yarn build
20+
- yarn test:ci && codecov --disable=gcov
21+
after_success:
22+
- |
23+
if [ "$TRAVIS_PULL_REQUEST" == "false" ] && [ "$TRAVIS_BRANCH" == "next" ]; then
24+
git config --global user.name "React Native Elements CI"
25+
echo -e "machine github.com\n login react-native-elements-ci\n password $GITHUB_TOKEN" >> ~/.netrc
26+
cd website && yarn && GIT_USER=react-native-elements-ci yarn publish-gh-pages
27+
fi

0 commit comments

Comments
 (0)