Error codes

[elena-kolevska]

Description

This PR adds a page that explains the usage structure of the richer errors model in Dapr.

Issue reference

#3907

Please follow this checklist before submitting:

• Commits are signed with Developer Certificate of Origin (DCO - learn more)
• Read the contribution guide
• New file and folder names are globally unique

N/A:

• Page references use shortcodes instead of markdown or URL links
• Images use HTML style and have alternative text
• Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:

[elena-kolevska]

@msfussell pls let me know if this structure looks ok; I'm not sure if we want a new menu item for errors, but I couldn't see it anywhere else.

[github-actions]

Stale PR, paging all reviewers

[github-actions]

Stale PR, paging all reviewers

[hhunter-ms]

quick initial grammar review

[elena-kolevska]

Thanks for the review @hhunter-ms . All done!

[msfussell]

Comments on what you have here so far. Primarily we should refer to these as enhanced error message rather than richer.
However there are two additional things that we need to add

1. Any guidance on using (consuming) these errors. This may be language specific and therefore hard, but would be good if possible
2. Guidance on generating these. There should at least be some guidance with a couple of examples of when to use which field in the case of Dapr errors. You have given one example, but can we have at least 2 more to learn from?

[msfussell]

Suggested change

	# Dapr Error Handling: Understanding the Error Models
	# Error handling: Understanding errors model and reporting

[msfussell]

This should be moved to after the first paragraph in the enhanced error section above, since this is what people will use to create/understand errors.

[elena-kolevska]

So switch the order of the grpc and json examples, right? They're the same thing, it's just that we're showing the json representation (used in http connections) and the proto structure for gRPC connections.

[elena-kolevska]

Re: the suggestion to use the term "enhanced" instead of "richer" error model.
It might make sense to keep "Richer", because it is the name of the model, defined by grpc, and is a standard in the community. It's a name people already recognise, so I would consider adopting it too.

[msfussell]

Re: the suggestion to use the term "enhanced" instead of "richer" error model. It might make sense to keep "Richer", because it is the name of the model, defined by grpc, and is a standard in the community. It's a name people already recognise, so I would consider adopting it too.
Agree. If this is the term used by gRPC then we should keep this.

[msfussell]

@elena-kolevska - This looks good. I would just add at the end of the doc these references

Related Links

• Authoring error codes
• Using error codes in the Go SDK

[elena-kolevska]

Thank @msfussell. Done.

[msfussell]

LGTM!!