Design 'app model' file
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 807
- Avg merge
- 10h 12m
- Merged PRs (30d)
- 7
Description
We want to keep some workspace-local metadata that maps the user's code to deployed Lambda functions (and serverless apps). This is the 'app model' file concept that's been floated around and is similar in concept to the Cloud9 .application.json file.
This task is to design what we'll do in VSCode. Output will be a design doc for discussion and one or more tasks for implementation.
* Can we re-use the Cloud9 file (and perhaps the jetBrains version, if it should exist)? How do we keep in sync with them if so?
* Do we need our own file? If so, what's the format and what's the round trip story with Cloud9?
I'm sure other issues and considerations will come forward when we start to think this through more deeply!
Contributor guide
Research direction
Start by reviewing the issue's app model concept and the Cloud9 .application.json format, then investigate whether a JetBrains equivalent exists. Compare reuse versus a VSCode-specific file, including synchronization and Cloud9 round-trip concerns, and document the proposed design with follow-up implementation tasks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- cloud, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100