Skip to content

feat: Export the ErrInvalidIDType error.

Florian Forsterrequested to merge
fforster/err_invalid_id_type into main

This change standardizes error handling across multiple test files by replacing specific error message checks with a more consistent approach. Instead of checking for exact error message strings like "invalid ID type 1.5, the ID must be an int or a string", the code now uses assert.ErrorIs(t, err, ErrInvalidIDType) or require.ErrorIs(t, err, ErrInvalidIDType).

This modification makes the tests more maintainable by:

  1. Using a predefined error constant (ErrInvalidIDType) instead of hardcoded error strings
  2. Focusing on the error type rather than its exact message
  3. Creating consistency across all test files in the codebase

The change affects multiple test files including access requests, audit events, award emojis, boards, and branches tests, but doesn't alter the actual functionality being tested.

Merge request reports