Skip to content

WPB-28093: add dedicated Meeting errors description - #5455

Merged
blackheaven merged 5 commits into
developfrom
gdifolco/WPB-28083-meetings-errors
Aug 19, 2026
Merged

WPB-28093: add dedicated Meeting errors description#5455
blackheaven merged 5 commits into
developfrom
gdifolco/WPB-28083-meetings-errors

Conversation

@blackheaven

@blackheaven blackheaven commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

https://wearezeta.atlassian.net/browse/WPB-28093

Checklist

  • Add a new entry in an appropriate subdirectory of changelog.d
  • Read and follow the PR guidelines

@blackheaven
blackheaven requested review from a team as code owners August 17, 2026 16:42
@blackheaven
blackheaven force-pushed the gdifolco/WPB-28083-meetings-errors branch from 5ad4a79 to 8725784 Compare August 17, 2026 16:42
@zebot zebot added the ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist label Aug 17, 2026
@blackheaven
blackheaven force-pushed the gdifolco/WPB-28083-meetings-errors branch from 104a466 to 697976c Compare August 17, 2026 17:02
@blackheaven blackheaven changed the title WPB-28083: add dedicated Meeting errors description WPB-28093: add dedicated Meeting errors description Aug 18, 2026
-- @CanThrow 'MeetingError'@. Every constructor keeps the @invalid-op@ label
-- but carries an explicit message; 'InvalidTimes' additionally records which
-- validation failed.
data MeetingError

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

(Off topic for this PR, but why do we categorize errors by "micro"-services rather than subsystems?)

type instance MapError 'CodeStoreNotFound = 'StaticError 404 "code-store-not-found" "Code store not found"

-- | Errors raised by the meetings subsystem, exposed at the API level via
-- @CanThrow 'MeetingError'@. Every constructor keeps the @invalid-op@ label

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why not different labels? Clients need the label to understand the error and render / translate it for the user. "message" is human-readable and should be ignored by client logic.

On the other hand, maybe you don't want to mess with the API for compatibility reasons. Your call.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

It's mostly for compatibility reasons.

Currently clients don't interpret failures, but a generic description make debuggi_ng so much harder.

@blackheaven
blackheaven force-pushed the gdifolco/WPB-28080-meetings-update-24h branch from fcf675a to 6335643 Compare August 19, 2026 10:53
Base automatically changed from gdifolco/WPB-28080-meetings-update-24h to develop August 19, 2026 13:43
@blackheaven
blackheaven force-pushed the gdifolco/WPB-28083-meetings-errors branch from e4a8c69 to 1647724 Compare August 19, 2026 14:20
@blackheaven
blackheaven merged commit 4f5c093 into develop Aug 19, 2026
9 checks passed
@blackheaven
blackheaven deleted the gdifolco/WPB-28083-meetings-errors branch August 19, 2026 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants