| --- |
| name: "\U0001F680Feature request" |
| about: Suggest a feature for rules_typescript |
| |
| --- |
| <!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅 |
| |
| Oh hi there! 😄 |
| |
| To expedite issue processing please search open and closed issues before submitting a new one. |
| Existing issues often contain information about workarounds, resolution, or progress updates. |
| |
| 🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅--> |
| |
| |
| # 🚀 feature request |
| |
| ### Relevant Rules |
| |
| <!-- Tell us if you want to add a feature to an existing rule or add a new rule --> |
| |
| <!-- |
| |
| If you're looking for a new rule first make sure you check awesome-bazel for an |
| curated list of existing bazel rules https://github.com/jin/awesome-bazel |
| |
| If you don't find what you're looking for there, before opening a feature request make sure |
| this repository is the right place for that. |
| |
| We have a list of requirements that the rules in this repository need to follow. |
| You can check them in the README.md file of the project. |
| |
| --> |
| |
| ### Description |
| |
| <!-- ✍️--> A clear and concise description of the problem or missing capability... |
| |
| |
| ### Describe the solution you'd like |
| |
| <!-- ✍️--> If you have a solution in mind, please describe it. |
| |
| |
| ### Describe alternatives you've considered |
| |
| <!-- ✍️--> Have you considered any alternative solutions or workarounds? |
