Only generate `@error` `message` getter when defined in the model (#1441)
We are currently generating a useless `message` getter that returns `None` even when the `message` field is not defined in the model. Granted, in the client this field is _almost always_ there, because the `AddErrorMessage` model transformer is applied unless the user opts out in their `smithy-build.json`.
Loading
Please register or sign in to comment