|
| 1 | +name: Feature Request |
| 2 | +description: Create a feature request to make PyScript even better |
| 3 | +labels: ["type: enhancement", "needs-triage"] |
| 4 | +body: |
| 5 | +- type: markdown |
| 6 | + attributes: |
| 7 | + value: | |
| 8 | + ### Thanks for helping PyScript! 🐍 |
| 9 | +
|
| 10 | + Going through feature requests and issues takes up a lot of time, so please be so kind and take a few minutes to fill out all the areas to the best of your ability. |
| 11 | +
|
| 12 | + There will always be more great ideas than there is time to do them, and so we will need to selectively close issues that don't provide enough information, so everyone can focus our time on helping people like you who fill out the form completely. Thank you for your collaboration! |
| 13 | +
|
| 14 | + There are also already a lot of open requests, so please take 2 minutes and search through existing ones to see if your idea already exists. If you find something close, please upvote that request and comment. |
| 15 | +
|
| 16 | + Thanks for helping PyScript be amazing. We are nothing without people like you helping build a better community 💐! |
| 17 | +
|
| 18 | + ### Lets make sure you are in the right place. If you have an idea/request for: |
| 19 | +
|
| 20 | + - #### A specific package/library (such as pandas or scikit learn): |
| 21 | +
|
| 22 | + Search for that respective library on github repo or website. You will have much more success there. |
| 23 | +
|
| 24 | + - #### A general Python question/feature request: |
| 25 | +
|
| 26 | + Try out a forum post [here](https://discuss.python.org/c/users/7) |
| 27 | +
|
| 28 | +- type: checkboxes |
| 29 | + id: checks |
| 30 | + attributes: |
| 31 | + label: Checklist |
| 32 | + description: Please confirm and check all the following options |
| 33 | + options: |
| 34 | + - label: I added a descriptive title |
| 35 | + required: true |
| 36 | + - label: I searched for other feature requests and couldn't find a duplicate (including also the ``type-feature`` tag) |
| 37 | + required: true |
| 38 | + - label: I confirmed that it's not related to another project are area (see the above section) |
| 39 | + required: true |
| 40 | +- type: textarea |
| 41 | + id: request-idea |
| 42 | + attributes: |
| 43 | + label: What is the idea? |
| 44 | + description: Describe what the feature is and the desired state |
| 45 | + placeholder: This feature would allow any user of PyScript to type in a simple command in the console and show all variables currently in use |
| 46 | + validations: |
| 47 | + required: true |
| 48 | +- type: textarea |
| 49 | + id: why |
| 50 | + attributes: |
| 51 | + label: Why is this needed |
| 52 | + description: | |
| 53 | + Who would benefit from this and why would this add value to them? What problem does this solve? |
| 54 | + placeholder: This would benefit users who would like to see what is being used so they can learn and debug faster |
| 55 | +- type: textarea |
| 56 | + id: what |
| 57 | + attributes: |
| 58 | + label: What should happen? |
| 59 | + description: | |
| 60 | + What should be the user experience with the feature? Describe from a user perpective what they would do and see |
| 61 | + placeholder: A user would type in ``PyScript debug`` in the browser console and see a list of all variables created. |
| 62 | +- type: textarea |
| 63 | + id: context |
| 64 | + attributes: |
| 65 | + label: Additional Context |
| 66 | + description: | |
| 67 | + Is there any other information that you think would be valuable for the team to know? |
0 commit comments