aws / aws/codecatalyst-blueprints
Debugging synth failures as an author is pretty difficult
Open
- Dominant language
- TypeScript
- Stars
- 58
- Forks
- 22
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
Expose full stack trace if you're in author
Contributor guide
Research direction
Start by locating the synth failure handling and the path that detects author context. Reproduce a synth failure as an author and compare the current error output with the full stack trace requirement. Done means author-mode failures expose the complete stack trace without changing non-author behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100