EclipseFdn / EclipseFdn/open-vsx.org
Claiming namespace `DataViewer`
- Dominant language
- TypeScript
- Stars
- 394
- Forks
- 145
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
### Namespace
DataViewer
### Ownership
- [x] The namespace is not currently owned on Open VSX (verify by a search on [open-vsx.org](https://open-vsx.org))
### Account Age
- [x] The GitHub ID making this request has at least 12 months of public history
### VS Code Publisher with Repo
- [ ] The namespace is also a publisher account on the VS Code Marketplace (check by browsing https://marketplace.visualstudio.com/publishers/{publisher}) and has an extension published there with a repo specified in its package.json file.
### VS Code Publisher without Repo
- [x] The namespace is also a publisher account on the VS Code Marketplace and does not have published extensions or has published extensions with no GitHub repos.
### Not a VS Code Marketplace Publisher
- [ ] The namespace is not a publisher account on the VS Code Marketplace
### All Other Cases
- [ ] You are unable to provide the inputs required in the three options above. This option will take the longest to process.
### Claim evidence
I've now added a repository field to my extension's package.json, pointing to the public repo https://github.com/Yvonne1ru/dataviewer. The extension's Open VSX entry should now link to this repo.
This repo is the source for the extension's README images (the four guide0–3.png screenshots are hosted there and referenced from the README), and it also contains the OWNERSHIP.md file proving my connection to the namespace.
Could you please confirm the namespace claim? Many thanks!
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the namespace on open-vsx.org and check the VS Code Marketplace publisher page described in the checklist. Verify the extension's package.json repository field, the linked GitHub repository, and the ownership evidence, then confirm the namespace claim once the stated conditions are met.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 75/100