Skip to content

Conversation

loivsen
Copy link
Contributor

@loivsen loivsen commented Jul 2, 2024

Description

Shows a more detailed ApiError description
Are there any place I have missed?

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (minor updates related to the tooling or maintenance of the repository, does not impact compiled assets)

How to test?

  • Save something where it throws an ApiError: For example attempt to create a new Template with no name or alias.

@loivsen loivsen requested a review from leekelleher July 2, 2024 10:56
@loivsen loivsen marked this pull request as ready for review July 2, 2024 11:06
Copy link
Collaborator

@iOvergaard iOvergaard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice to see the errors starting to be shown. I added some suggestions down here. I think we should consider how to translate these messages as they are only fallback texts from the server. Do you know if they forward some sort of error code, we could hook in to?

@iOvergaard iOvergaard merged commit f092989 into main Jul 5, 2024
@iOvergaard iOvergaard deleted the v14/bugfix/show-correct-api-error-description branch July 5, 2024 08:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants