Skip to content

Better error messages with fix suggestions and docs links #1063

@patrikbraborec

Description

@patrikbraborec

Summary

Error messages should be actionable — they should suggest how to fix the problem and link to relevant documentation.

Action Items

  • Errors should suggest how to fix the problem (check mcpc, gh for inspiration)
  • Build API: wrong version returns generic 404 instead of a helpful error. CLI should surface better messages when the API returns unhelpful errors.
  • Include relevant docs links in error output (make sure it's .md, i.e. https://docs.apify.com/platform/proxy/usage.md)

Supersedes

Metadata

Metadata

Labels

t-toolingIssues with this label are in the ownership of the tooling team.

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