vscode-array-index-inlay

Dear extension author, Please publish this extension to the Open VSX marketplace. Context Unfortunately, as Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of files from it, in order to use VS Code extensions in non-Microsoft products, we kindly ask that you take ownership of the VS Code extension namespace in Open VSX and publish this extension on Open VSX. What is Open VSX? Why does it exist? Open VSX is a vendor neutral alternative to the MS marketplace used by most other derivatives of VS Code like VSCodium, Gitpod, OpenVSCode, Theia-based IDEs, and so on. You can read on about Open VSX at the Eclipse Foundation's Open VSX FAQ. How can you publish to Open VSX? The docs to publish an extension can be found here. This process is straightforward and shouldn't take too long. Essentially, you need an authentication token and to execute the command to publish your extension. There's also a doc explaining the whole process with an example GitHub Action workflow.

Describe the bug Hi there! Thanks so much for this plugin! It’s been super helpful for test creation—being able to visualize which test failed based on the index instead of searching for a needle in a haystack is a game-changer! I did notice a small formatting quirk:** when reaching index (_zero-based_), the spacing increases as if we’re at . From what I can tell, the same happens at when transitioning to , for example. !Image !Image In my case, I’m using a _zero-based array_. Switching the config to _one-based indexing_ resolved the issue. Just wanted to share this in case it helps! Reproduction System Info Used Package Manager pnpm Validations [x] Follow our Code of Conduct [x] Read the Contributing Guide. [x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. [x] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead. [x] The provided reproduction is a minimal reproducible of the bug. Contributions [ ] I am willing to submit a PR to fix this issue [ ] I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)