├── .github
├── ISSUE_TEMPLATE
│ ├── bug-report.yml
│ └── feature-request.yml
├── pull_request_template.md
└── workflows
│ ├── publish.yml
│ └── pull_preview.yml
├── .gitignore
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── babel.config.js
├── blog
├── 2024-08-03-first-blog
│ └── index.mdx
└── authors.yml
├── docs
├── dev_docs
│ ├── case.md
│ └── intro.md
└── user_docs
│ ├── fastpr.md
│ └── intro.md
├── docusaurus.config.ts
├── i18n
├── en
│ ├── code.json
│ ├── docusaurus-plugin-content-blog
│ │ ├── authors.yml
│ │ └── options.json
│ ├── docusaurus-plugin-content-docs
│ │ ├── current.json
│ │ └── current
│ │ │ └── user_docs
│ │ │ └── intro.md
│ └── docusaurus-theme-classic
│ │ └── navbar.json
└── zh
│ ├── code.json
│ ├── docusaurus-plugin-content-blog
│ └── options.json
│ ├── docusaurus-plugin-content-docs
│ └── current.json
│ └── docusaurus-theme-classic
│ └── navbar.json
├── package-lock.json
├── package.json
├── sidebars.ts
├── src
├── components
│ └── HomepageFeatures
│ │ ├── index.tsx
│ │ └── styles.module.css
├── css
│ └── custom.css
├── pages
│ ├── index.module.css
│ └── index.tsx
└── theme
│ └── Layout
│ └── index.tsx
├── static
├── .nojekyll
└── img
│ ├── easy_to_use.svg
│ ├── fastpr-example1.png
│ ├── fastpr-example2.png
│ ├── fastpr-example3.png
│ ├── favicon.ico
│ ├── keep-service-worker-devtools-open.jpeg
│ ├── logos
│ ├── hypercrx-dark.svg
│ ├── hypercrx.png
│ └── hypercrx.svg
│ ├── rich_metrics.svg
│ └── various_applications.svg
└── tsconfig.json
/.github/ISSUE_TEMPLATE/bug-report.yml:
--------------------------------------------------------------------------------
1 | name: 🐛 Bug report
2 | description: Create a bug report
3 | body:
4 | - type: checkboxes
5 | attributes:
6 | label: Are you certain it's a bug?
7 | description: This issue tracker is only for reporting bugs.
8 | options:
9 | - label: Yes, it looks like a bug
10 | required: true
11 | - type: checkboxes
12 | attributes:
13 | label: Are you sure this is not an issue in Docusaurus?
14 | description: If this is a Docusaurus issue, report it at https://github.com/facebook/docusaurus/issues.
15 | options:
16 | - label: It is not a Docusaurus issue
17 | required: true
18 | - type: checkboxes
19 | attributes:
20 | label: Is there an existing issue for this?
21 | description: Please search to see if an issue already exists
22 | options:
23 | - label: I have searched existing issues, it hasn't been reported yet
24 | required: true
25 | - type: textarea
26 | attributes:
27 | label: Issue description
28 | validations:
29 | required: true
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature-request.yml:
--------------------------------------------------------------------------------
1 | name: 🎉 Feature request
2 | description: Suggest an idea
3 | body:
4 | - type: checkboxes
5 | attributes:
6 | label: Is there an existing issue for this?
7 | description: Please search to see if an issue already exists
8 | options:
9 | - label: I have searched existing issues, it hasn't been reported yet
10 | required: true
11 | - type: textarea
12 | attributes:
13 | label: Use case description
14 | description: Describe the problem (use case) that needs to be solved
15 | validations:
16 | required: true
17 | - type: textarea
18 | attributes:
19 | label: Proposed solution (optional)
20 | description: |
21 | e.g. propose how the configuration of the new feature could look
--------------------------------------------------------------------------------
/.github/pull_request_template.md:
--------------------------------------------------------------------------------
1 | ## Description
2 |
3 | Describe your PR here.
4 |
5 | ## Resolved issues
6 |
7 | Closes #1
8 |
9 | ### Before submitting the PR, please take the following into consideration
10 | - [ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. If you don't have an issue, please create one.
11 | - [ ] Prefix your PR title with `feat: `, `fix: `, `chore: `, `docs:`, or `refactor:`.
12 | - [ ] The description should clearly illustrate what problems it solves.
13 | - [ ] Ensure that the commit messages follow our guidelines.
14 | - [ ] Resolve merge conflicts (if any).
15 | - [ ] Make sure that the current branch is upto date with the `master` branch.
16 |
--------------------------------------------------------------------------------
/.github/workflows/publish.yml:
--------------------------------------------------------------------------------
1 | name: publish
2 |
3 | on:
4 | push:
5 | branches: [ master ]
6 | workflow_dispatch:
7 |
8 | jobs:
9 | publish:
10 | runs-on: ubuntu-latest
11 |
12 | steps:
13 | - name: Check out repository
14 | uses: actions/checkout@v4
15 |
16 | - name: Setup node 18 env
17 | uses: actions/setup-node@v4
18 | with:
19 | node-version: '18'
20 | cache: "npm"
21 |
22 | - name: build
23 | run: |
24 | git config --global url."https://github.com/".insteadOf git://github.com/
25 | npm install
26 | npm run build
27 |
28 | - name: Publish to OSS
29 | uses: tvrcgo/oss-action@master
30 | with:
31 | key-id: ${{ secrets.OSS_ACCESS_KEY_ID }}
32 | key-secret: ${{ secrets.OSS_ACCESS_KEY_SECRET }}
33 | region: ${{ secrets.OSS_REGION }}
34 | bucket: ${{ secrets.OSS_BUCKET }}
35 | assets: |
36 | ./build/**:${{ secrets.OSS_TARGET_PATH }}
37 |
--------------------------------------------------------------------------------
/.github/workflows/pull_preview.yml:
--------------------------------------------------------------------------------
1 | name: pr_test
2 |
3 | on:
4 | issue_comment:
5 | types: [created]
6 | workflow_dispatch:
7 |
8 | jobs:
9 | preview:
10 | if: github.event.issue.pull_request
11 | runs-on: ubuntu-latest
12 |
13 | steps:
14 |
15 | - name: Check comment command
16 | uses: actions-ecosystem/action-regex-match@v2
17 | id: regex-match
18 | with:
19 | text: ${{ github.event.comment.body }}
20 | regex: '^/preview$'
21 |
22 | - uses: actions/github-script@v3
23 | id: get-pr
24 | if: ${{ steps.regex-match.outputs.match != '' }}
25 | with:
26 | script: |
27 | const request = {
28 | owner: context.repo.owner,
29 | repo: context.repo.repo,
30 | pull_number: context.issue.number
31 | }
32 | core.info(`Getting PR #${request.pull_number} from ${request.owner}/${request.repo}`)
33 | try {
34 | const result = await github.pulls.get(request)
35 | return result.data
36 | } catch (err) {
37 | core.setFailed(`Request failed with error ${err}`)
38 | }
39 |
40 | - name: Check out pull request head
41 | if: ${{ steps.regex-match.outputs.match != '' }}
42 | uses: actions/checkout@v4
43 | with:
44 | repository: ${{ fromJSON(steps.get-pr.outputs.result).head.repo.full_name }}
45 | ref: ${{ fromJSON(steps.get-pr.outputs.result).head.sha }}
46 |
47 | - name: Setup node 18 env
48 | if: ${{ steps.regex-match.outputs.match != '' }}
49 | uses: actions/setup-node@v4
50 | with:
51 | node-version: '18'
52 | cache: "npm"
53 |
54 | - name: Build the website
55 | if: ${{ steps.regex-match.outputs.match != '' }}
56 | run: |
57 | git config --global url."https://github.com/".insteadOf git://github.com/
58 | npm install
59 | PULL_NUM=${{ github.event.issue.number }} npm run build
60 |
61 | - name: Upload to OSS
62 | if: ${{ steps.regex-match.outputs.match != '' }}
63 | uses: tvrcgo/oss-action@master
64 | with:
65 | key-id: ${{ secrets.OSS_ACCESS_KEY_ID }}
66 | key-secret: ${{ secrets.OSS_ACCESS_KEY_SECRET }}
67 | region: ${{ secrets.OSS_REGION }}
68 | bucket: ${{ secrets.OSS_BUCKET }}
69 | assets: |
70 | ./build/**:${{ secrets.OSS_TARGET_PATH }}pull_${{ github.event.issue.number }}/
71 |
72 | - name: Create comment
73 | if: ${{ steps.regex-match.outputs.match != '' }}
74 | uses: peter-evans/create-or-update-comment@v4
75 | with:
76 | issue-number: ${{ github.event.issue.number }}
77 | body: 🪧The website for this PR is deployed at https://hypercrx.cn${{ secrets.OSS_TARGET_PATH }}pull_${{ github.event.issue.number }}/
78 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # Dependencies
2 | /node_modules
3 |
4 | # Production
5 | /build
6 |
7 | # Generated files
8 | .docusaurus
9 | .cache-loader
10 |
11 | # Misc
12 | .DS_Store
13 | .env.local
14 | .env.development.local
15 | .env.test.local
16 | .env.production.local
17 |
18 | npm-debug.log*
19 | yarn-debug.log*
20 | yarn-error.log*
21 |
22 | .vscode
23 | publish.sh
24 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Working by Forking
2 | Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or just head straight to the command line:
3 |
4 | ## Clone your fork to your local machine
5 | ```
6 | git clone git@github.com:USERNAME/FORKED-PROJECT.git
7 | ```
8 | Keeping Your Fork Up to Date
9 | While this isn't an absolutely necessary step, if you plan on doing anything more than just a tiny quick fix, you'll want to make sure you keep your fork up to date by tracking the original "upstream" repo that you forked. To do this, you'll need to add a remote:
10 |
11 | ## Add 'upstream' repo to list of remotes
12 | ```
13 | git remote add upstream https://github.com/hypertrons/hypercrx-website.git
14 | ```
15 |
16 | ## Verify the new remote named 'upstream'
17 | ```
18 | git remote -v
19 | ```
20 | Whenever you want to update your fork with the latest upstream changes, you'll need to first fetch the upstream repo's branches and latest commits to bring them into your repository:
21 |
22 | ## Fetch from upstream remote
23 | ```
24 | git fetch upstream
25 | ```
26 |
27 | ## View all branches, including those from upstream
28 | ```
29 | git branch -va
30 | ```
31 | Now, checkout your own master branch and merge the upstream repo's master branch:
32 |
33 | ## Checkout your master branch and merge upstream
34 | ```
35 | git checkout master
36 | git merge upstream/master
37 | ```
38 | If there are no unique commits on the local master branch, git will simply perform a fast-forward. However, if you have been making changes on master (in the vast majority of cases you probably shouldn't be - see the next section), you may have to deal with conflicts. When doing so, be careful to respect the changes made upstream.
39 |
40 | Now, your local master branch is up-to-date with everything modified upstream.
41 |
42 | **Create a Branch** (doing your work)
43 | Whenever you begin work on a new feature or bugfix, it's important that you create a new branch. Not only is it proper git workflow, but it also keeps your changes organized and separated from the master branch so that you can easily submit and manage multiple pull requests for every task you complete.
44 |
45 | To create a new branch and start working on it, perform the following flow.
46 |
47 | ## Checkout the master branch - you want your new branch to come from master
48 | ```
49 | git checkout master
50 | ```
51 |
52 | ## Create a new branch (give your branch its own simple informative name)
53 | For enhancements use `feature/your_username/issue#` or `feature/your_username/name_of_feature`
54 |
55 | For bugs use `bug/your_username/issue#` or `bug/your_username/name_of_bug`
56 |
57 | ```
58 | git branch feature/jdoe/567
59 | ```
60 |
61 | ## Switch to your new branch
62 | ```
63 | git checkout feature/jdoe/567
64 | ```
65 | Now, go to town hacking away and making whatever changes you want to.
66 |
67 | ## Submitting your changes (a Pull Request)
68 | Prior to submitting your pull request, you might want to do a few things to clean up your branch and make it as simple as possible for the original repo's maintainer to test, accept, and merge your work.
69 |
70 | In the time that you've been working on your changes, if any commits have been made to the upstream master branch, you will need to rebase your development branch so that merging it will be a simple fast-forward that won't require any conflict resolution work.
71 |
72 | ## Fetch upstream master and merge with your repo's master branch
73 | ```
74 | git fetch upstream
75 | git checkout master
76 | git merge upstream/master
77 | ```
78 |
79 | ## If there were any new commits, rebase your development branch
80 | ```
81 | git checkout feature/jdoe/567
82 | git rebase master
83 | ```
84 | Now, it may be desirable to squash some of your smaller commits down into a small number of larger more cohesive commits. You can do this with an interactive rebase:
85 |
86 | ## Rebase all commits on your development branch
87 | ```
88 | git checkout
89 | git rebase -i master
90 | ```
91 | This will open up a text editor where you can specify which commits to squash.
92 |
93 | ## Signing-off on Commits (Developer Certificate of Origin)
94 |
95 | To contribute to this project, you must agree to the Developer Certificate of
96 | Origin (DCO) for each commit you make. The DCO is a simple statement that you,
97 | as a contributor, have the legal right to make the contribution.
98 |
99 | See the [DCO](https://developercertificate.org) file for the full text of what you must agree to
100 | and how it works [here](https://github.com/probot/dco#how-it-works).
101 | To signify that you agree to the DCO for contributions, you simply add a line to each of your
102 | git commit messages:
103 |
104 | ```
105 | Signed-off-by: Jane Smith
106 | ```
107 |
108 | In most cases, you can add this signoff to your commit automatically with the
109 | `-s` or `--signoff` flag to `git commit`. You must use your real name and a reachable email
110 | address (sorry, no pseudonyms or anonymous contributions). An example of signing off on a commit:
111 | ```
112 | $ commit -s -m “my commit message w/signoff”
113 | ```
114 |
115 | To ensure all your commits are signed, you may choose to add this alias to your global ```.gitconfig```:
116 |
117 | *~/.gitconfig*
118 | ```
119 | [alias]
120 | amend = commit -s --amend
121 | cm = commit -s -m
122 | commit = commit -s
123 | ```
124 |
125 | ## Mermaid Diagrams
126 | If you are adding a new Mermaid diagram, you can use the [getting-started](https://mermaid.js.org/intro/getting-started.html) documentation to get started. You can also use the [Mermaid Live Editor](https://mermaid-js.github.io/mermaid-live-editor/) to create and preview your diagrams.
127 |
128 | ## Submitting
129 | Once you've committed and pushed all of your changes to GitHub, go to the page for your fork on GitHub, select your development branch, and click the pull request button. If you need to make any adjustments to your pull request, just push the updates to GitHub. Your pull request will automatically track the changes on your development branch and update.
130 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | Apache License
2 | Version 2.0, January 2004
3 | http://www.apache.org/licenses/
4 |
5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6 |
7 | 1. Definitions.
8 |
9 | "License" shall mean the terms and conditions for use, reproduction,
10 | and distribution as defined by Sections 1 through 9 of this document.
11 |
12 | "Licensor" shall mean the copyright owner or entity authorized by
13 | the copyright owner that is granting the License.
14 |
15 | "Legal Entity" shall mean the union of the acting entity and all
16 | other entities that control, are controlled by, or are under common
17 | control with that entity. For the purposes of this definition,
18 | "control" means (i) the power, direct or indirect, to cause the
19 | direction or management of such entity, whether by contract or
20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the
21 | outstanding shares, or (iii) beneficial ownership of such entity.
22 |
23 | "You" (or "Your") shall mean an individual or Legal Entity
24 | exercising permissions granted by this License.
25 |
26 | "Source" form shall mean the preferred form for making modifications,
27 | including but not limited to software source code, documentation
28 | source, and configuration files.
29 |
30 | "Object" form shall mean any form resulting from mechanical
31 | transformation or translation of a Source form, including but
32 | not limited to compiled object code, generated documentation,
33 | and conversions to other media types.
34 |
35 | "Work" shall mean the work of authorship, whether in Source or
36 | Object form, made available under the License, as indicated by a
37 | copyright notice that is included in or attached to the work
38 | (an example is provided in the Appendix below).
39 |
40 | "Derivative Works" shall mean any work, whether in Source or Object
41 | form, that is based on (or derived from) the Work and for which the
42 | editorial revisions, annotations, elaborations, or other modifications
43 | represent, as a whole, an original work of authorship. For the purposes
44 | of this License, Derivative Works shall not include works that remain
45 | separable from, or merely link (or bind by name) to the interfaces of,
46 | the Work and Derivative Works thereof.
47 |
48 | "Contribution" shall mean any work of authorship, including
49 | the original version of the Work and any modifications or additions
50 | to that Work or Derivative Works thereof, that is intentionally
51 | submitted to Licensor for inclusion in the Work by the copyright owner
52 | or by an individual or Legal Entity authorized to submit on behalf of
53 | the copyright owner. For the purposes of this definition, "submitted"
54 | means any form of electronic, verbal, or written communication sent
55 | to the Licensor or its representatives, including but not limited to
56 | communication on electronic mailing lists, source code control systems,
57 | and issue tracking systems that are managed by, or on behalf of, the
58 | Licensor for the purpose of discussing and improving the Work, but
59 | excluding communication that is conspicuously marked or otherwise
60 | designated in writing by the copyright owner as "Not a Contribution."
61 |
62 | "Contributor" shall mean Licensor and any individual or Legal Entity
63 | on behalf of whom a Contribution has been received by Licensor and
64 | subsequently incorporated within the Work.
65 |
66 | 2. Grant of Copyright License. Subject to the terms and conditions of
67 | this License, each Contributor hereby grants to You a perpetual,
68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69 | copyright license to reproduce, prepare Derivative Works of,
70 | publicly display, publicly perform, sublicense, and distribute the
71 | Work and such Derivative Works in Source or Object form.
72 |
73 | 3. Grant of Patent License. Subject to the terms and conditions of
74 | this License, each Contributor hereby grants to You a perpetual,
75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76 | (except as stated in this section) patent license to make, have made,
77 | use, offer to sell, sell, import, and otherwise transfer the Work,
78 | where such license applies only to those patent claims licensable
79 | by such Contributor that are necessarily infringed by their
80 | Contribution(s) alone or by combination of their Contribution(s)
81 | with the Work to which such Contribution(s) was submitted. If You
82 | institute patent litigation against any entity (including a
83 | cross-claim or counterclaim in a lawsuit) alleging that the Work
84 | or a Contribution incorporated within the Work constitutes direct
85 | or contributory patent infringement, then any patent licenses
86 | granted to You under this License for that Work shall terminate
87 | as of the date such litigation is filed.
88 |
89 | 4. Redistribution. You may reproduce and distribute copies of the
90 | Work or Derivative Works thereof in any medium, with or without
91 | modifications, and in Source or Object form, provided that You
92 | meet the following conditions:
93 |
94 | (a) You must give any other recipients of the Work or
95 | Derivative Works a copy of this License; and
96 |
97 | (b) You must cause any modified files to carry prominent notices
98 | stating that You changed the files; and
99 |
100 | (c) You must retain, in the Source form of any Derivative Works
101 | that You distribute, all copyright, patent, trademark, and
102 | attribution notices from the Source form of the Work,
103 | excluding those notices that do not pertain to any part of
104 | the Derivative Works; and
105 |
106 | (d) If the Work includes a "NOTICE" text file as part of its
107 | distribution, then any Derivative Works that You distribute must
108 | include a readable copy of the attribution notices contained
109 | within such NOTICE file, excluding those notices that do not
110 | pertain to any part of the Derivative Works, in at least one
111 | of the following places: within a NOTICE text file distributed
112 | as part of the Derivative Works; within the Source form or
113 | documentation, if provided along with the Derivative Works; or,
114 | within a display generated by the Derivative Works, if and
115 | wherever such third-party notices normally appear. The contents
116 | of the NOTICE file are for informational purposes only and
117 | do not modify the License. You may add Your own attribution
118 | notices within Derivative Works that You distribute, alongside
119 | or as an addendum to the NOTICE text from the Work, provided
120 | that such additional attribution notices cannot be construed
121 | as modifying the License.
122 |
123 | You may add Your own copyright statement to Your modifications and
124 | may provide additional or different license terms and conditions
125 | for use, reproduction, or distribution of Your modifications, or
126 | for any such Derivative Works as a whole, provided Your use,
127 | reproduction, and distribution of the Work otherwise complies with
128 | the conditions stated in this License.
129 |
130 | 5. Submission of Contributions. Unless You explicitly state otherwise,
131 | any Contribution intentionally submitted for inclusion in the Work
132 | by You to the Licensor shall be under the terms and conditions of
133 | this License, without any additional terms or conditions.
134 | Notwithstanding the above, nothing herein shall supersede or modify
135 | the terms of any separate license agreement you may have executed
136 | with Licensor regarding such Contributions.
137 |
138 | 6. Trademarks. This License does not grant permission to use the trade
139 | names, trademarks, service marks, or product names of the Licensor,
140 | except as required for reasonable and customary use in describing the
141 | origin of the Work and reproducing the content of the NOTICE file.
142 |
143 | 7. Disclaimer of Warranty. Unless required by applicable law or
144 | agreed to in writing, Licensor provides the Work (and each
145 | Contributor provides its Contributions) on an "AS IS" BASIS,
146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147 | implied, including, without limitation, any warranties or conditions
148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149 | PARTICULAR PURPOSE. You are solely responsible for determining the
150 | appropriateness of using or redistributing the Work and assume any
151 | risks associated with Your exercise of permissions under this License.
152 |
153 | 8. Limitation of Liability. In no event and under no legal theory,
154 | whether in tort (including negligence), contract, or otherwise,
155 | unless required by applicable law (such as deliberate and grossly
156 | negligent acts) or agreed to in writing, shall any Contributor be
157 | liable to You for damages, including any direct, indirect, special,
158 | incidental, or consequential damages of any character arising as a
159 | result of this License or out of the use or inability to use the
160 | Work (including but not limited to damages for loss of goodwill,
161 | work stoppage, computer failure or malfunction, or any and all
162 | other commercial damages or losses), even if such Contributor
163 | has been advised of the possibility of such damages.
164 |
165 | 9. Accepting Warranty or Additional Liability. While redistributing
166 | the Work or Derivative Works thereof, You may choose to offer,
167 | and charge a fee for, acceptance of support, warranty, indemnity,
168 | or other liability obligations and/or rights consistent with this
169 | License. However, in accepting such obligations, You may act only
170 | on Your own behalf and on Your sole responsibility, not on behalf
171 | of any other Contributor, and only if You agree to indemnify,
172 | defend, and hold each Contributor harmless for any liability
173 | incurred by, or claims asserted against, such Contributor by reason
174 | of your accepting any such warranty or additional liability.
175 |
176 | END OF TERMS AND CONDITIONS
177 |
178 | APPENDIX: How to apply the Apache License to your work.
179 |
180 | To apply the Apache License to your work, attach the following
181 | boilerplate notice, with the fields enclosed by brackets "[]"
182 | replaced with your own identifying information. (Don't include
183 | the brackets!) The text should be enclosed in the appropriate
184 | comment syntax for the file format. We also recommend that a
185 | file or class name and description of purpose be included on the
186 | same "printed page" as the copyright notice for easier
187 | identification within third-party archives.
188 |
189 | Copyright [yyyy] [name of copyright owner]
190 |
191 | Licensed under the Apache License, Version 2.0 (the "License");
192 | you may not use this file except in compliance with the License.
193 | You may obtain a copy of the License at
194 |
195 | http://www.apache.org/licenses/LICENSE-2.0
196 |
197 | Unless required by applicable law or agreed to in writing, software
198 | distributed under the License is distributed on an "AS IS" BASIS,
199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200 | See the License for the specific language governing permissions and
201 | limitations under the License.
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |