Feature Request: View into Resource Partials
Open
Nobody has claimed this yet.
Aspect: UX
Triage: Feature Request
- Dominant language
- TypeScript
- Stars
- 41
- Forks
- 18
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 3
Description
Describe the problem
Now that Resource Partials are a thing it would be great if the VSCode extension could provide some visibility into their definitions when using them.
Possible Solution
I'm not terribly familiar with what sort of options might be available within VSCode; a couple of thoughts:
- Direct link to view resource partial definition
- An expansion view to view the remote partial inline with the document
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating how the VSCode extension handles Resource Partials when they are used. Compare the two proposed entry points—linking to the remote partial definition or expanding it inline—and define which behavior should count as complete before implementing or testing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100