Issues

Before You Start...

The issue list is reserved exclusively for bug reports and feature requests. That means we do not accept usage questions. If you open an issue that does not conform to the requirements, it will be closed immediately.

Why are we so strict about this?

The reason behind our strict issue policy

Maintaining open source projects, especially popular ones, is hard work. As Nimbu's user base has grown, we are getting more and more usage questions, bug reports, feature requests and pull requests every single day.

As a free and open source project, Nimbus also has limited maintainer bandwidth. That means the only way to ensure the project's sustainability is to:

Prioritize more concrete work (bug fixes and new features);
Improve issue triaging efficiency.

For (1), we have decided to use the GitHub issue lists exclusively for work that has well-defined, actionable goals. Questions and open ended discussions should be posted to mediums that are better suited for them.

For (2), we have found that issues that do not provide proper information upfront usually results in terribly inefficient back-and-forth communication just to extract the basic information needed for actual triaging. This is exactly why we have created this app: to ensure that every issue is created with the necessary information, and to save time on both sides.

Questions

For usage questions, please use the following resources:

Also try to search for your issue - it may have already been answered or even fixed in the development branch. However, if you find that an old, closed issue still persists in the latest version, you should open a new issue using the form below instead of commenting on the old issue.

Question Form

Your email:
I am opening an issue for (item):
Item name:
This is a: Bug Report Feature Report
Issue title:

FOR Bug Report

Vesion:

(Check if the issue is reproducible with the latest stable version of Vue.)

Link to minimal reproduction:

(If possible, use the SFC Playground to provide a reproduction. If it requires an actual build setup, you can use StackBlitz, CodeSandbox or provide a GitHub repo.

Please do not just fill in a random link. We will close your issue if you do that.)

Steps to reproduce:

(What do we need to do after opening your repro in order to make the bug happen? Clear and concise reproduction instructions are important for us to be able to triage your issue in a timely manner. Note that you can use Markdown to format lists and code.)

What is expected?:
What is actually happening?:
Any additional comments? (optional):

(e.g. some background/context of how you ran into this bug.)

Feature Report

What problem does this feature solve?:

(Explain your use case, context, and rationale behind this feature request. More importantly, what is the end user experience you are trying to build that led to the need for this feature?

An important design goal of Nimbus is keeping the API surface small and straightforward. In general, we only consider adding new features that solve a problem that cannot be easily dealt with using existing APIs (i.e. not just an alternative way of doing things that can already be done). The problem should also be common enough to justify the addition.)

What does the proposed API look like?:

(Describe how you propose to solve the problem and provide code samples of how the API would work once implemented. Note that you can use Markdown to format your code blocks.)

Announcements