Open skorfmann opened 1 year ago
Hi,
This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Hi,
This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Hi,
This issue hasn't seen activity in 90 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Hi,
This issue hasn't seen activity in 90 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Feature Spec
It's now easier for users to distinguish between SDK - as in internal Wing - errors and user land errors. Up until now, it was difficult to spot what the source of the error could be.
Take this very generic error message as an example:
Which now reads like this:
Use Cases
Implementation Notes
Triggered by this issue https://github.com/winglang/wing/issues/3289
The error was, that the generated client
and env
wasn't matching
WING_TOKEN_TFTOKEN_TOKEN_23
vsWING_TOKEN_TFTOKEN_TOKEN_21
Component
SDK
Community Notes