Skip to content

port in the EVR error handling package and add cloud-specific errors #44

@Akopti8

Description

@Akopti8
  • Unsure errors/return messages all start with either an upper case or lower case letter, avoid mixing the two
  • Use a colon followed by the error in error messages, instead of a comma for consistency
  • consistent error formatting
  • Double-check error messages to make sure you are being consistent with calling things objects verses keys.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions