generator output doesn't include result and reason by default for all packages
- Dominant language
- C#
- Stars
- 46
- Forks
- 63
- Avg merge
- 8d 4h
- Merged PRs (30d)
- 1
Description
**Is your feature request related to a problem? Please describe.**
The general discussion is that IntelliJ does not add `reason` and `result` to its overloaded definitions output. Same for Visual Studio. For VSCode you can use `run` or `emit` `reason and `result` WITHOUT explicitly defining those fields in the `commonDefinitions.json`
**Describe the solution you'd like**
I would like to not have to define `reason` or `result` in `commonDefinitions.json` since these fields are considered essential and required by the AWS Toolkit team.
**Describe alternatives you've considered**
1. Explicitly define `result` and `reason` in `commonDefinitions.json`.
**Additional context**
tbd
Contributor guide
Research direction
Start by tracing the generator output and inspecting commonDefinitions.json, then compare the IntelliJ, Visual Studio, and VSCode handling of run or emit. Done means reason and result appear by default for all package outputs without being explicitly defined in commonDefinitions.json.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100