Mirror: The highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

Update issue and PR templates

+62 -19
+3
.github/ISSUE_TEMPLATE.md
··· 1 + Please follow our issue templates: 2 + 3 + - https://github.com/FormidableLabs/urql/issues/new/choose
+16 -19
.github/ISSUE_TEMPLATE/bug_report.md
··· 3 3 about: Create a report to help us improve 4 4 title: '' 5 5 labels: "bug \U0001F41B" 6 - assignees: '' 7 - 8 - --- 6 + ---<!-- 7 + Please describe your bug clearly and concisely. 8 + Include a screenshot or a reproduction to illustrate 9 + the bug and how to reproduce it. 10 + Please also leave a note on what version of urql you're using 11 + and include a list of exchanges (if any). 12 + --> 9 13 10 - **Describe the bug** 11 - A clear and concise description of what the bug is. 14 + urql version & exchanges: 12 15 13 16 **Steps to reproduce** 14 - Steps to reproduce the behavior: 15 - 1. Go to '...' 16 - 2. Click on '....' 17 - 3. Scroll down to '....' 18 - 4. See error 17 + 18 + 1. 2. 19 19 20 20 **Expected behavior** 21 - A clear and concise description of what you expected to happen. 22 21 23 22 **Actual behavior** 24 - A clear and concise description of what is actually happening. 25 23 26 - **Additional context** 27 - Add any other context about the problem here. 28 - 29 - It offers a lot of help when you add a reproduction to your bug report, here are some templates to help you get started: 30 - 31 - - client: https://codesandbox.io/s/urql-issue-template-client-iui0o 32 - - server: https://codesandbox.io/s/urql-issue-template-server-0ufyz 24 + <!-- 25 + Your issue will be addressed much faster if you include a 26 + reproduction. Here are some templates to help you create one: 27 + - client: https://codesandbox.io/s/urql-issue-template-client-iui0o 28 + - server: https://codesandbox.io/s/urql-issue-template-server-0ufyz 29 + -->
+21
.github/ISSUE_TEMPLATE/question.md
··· 1 + --- 2 + name: '🤔 Questions and Help' 3 + about: Create a thread to ask your questions 4 + title: '' 5 + labels: "question \U0001F64B" 6 + ---<!-- 7 + 🚨 The issue tracker is not great for getting help! 8 + If you have a usage question, maybe consider asking 9 + for help on our Spectrum: 10 + https://spectrum.chat/urql 11 + 12 + If you'd like to go ahead remember to answer: 13 + - What problem are you running into? 14 + - What do you think may it be related to? 15 + - Is this covered in the docs? 16 + 17 + Please also leave a note on what version of urql you're using 18 + and include a list of exchanges (if any). 19 + --> 20 + 21 + urql version & exchanges:
+22
.github/PULL_REQUEST_TEMPLATE.md
··· 1 + <!-- 2 + Thanks for opening a pull request! We appreciate your dedication and help! 3 + Before submitting your pull request, please make sure to read our CONTRIBUTING guide. 4 + 5 + The best contribution is always a PR! However, if you're starting to work on a large 6 + change, it's best to make sure to open an issue first. 7 + 8 + If this PR is already related to an issue, please reference it like so: 9 + Resolves #123 10 + --> 11 + 12 + ## Summary 13 + 14 + <!-- What's the motivation of this change? What does it solve? --> 15 + 16 + ## Set of changes 17 + 18 + <!-- 19 + Roughly list the changes you've made and which packages are affected. 20 + Leave some notes on what may be noteworthy files you've changed. 21 + And lastly, please let us know if you think this is a breaking change. 22 + -->