[routing] every RoutingError variant has a moniker

In order to preserve UX in scrutiny, every routing error variant should
include a moniker indicating where the routing error happened. This is
necessary because today this information is guaranteed by the presence
of list of route segments in the scrutiny output, and in a future change
those route segments will be removed. This error type thus must carry
all the necessary information for diagnosing and resolving the issue it
signifies.

Change-Id: I9250b3923a213c7cf1db514f6b664a8a4dac77b7
Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1094672
Reviewed-by: Gary Bressler <geb@google.com>
Commit-Queue: Claire Gonyeo <cgonyeo@google.com>
29 files changed
tree: c66284330f70c60aab93c446c82a091423a631e8
  1. boards/
  2. build/
  3. bundles/
  4. docs/
  5. examples/
  6. infra/
  7. products/
  8. scripts/
  9. sdk/
  10. src/
  11. third_party/
  12. tools/
  13. zircon/
  14. .clang-format
  15. .clang-tidy
  16. .editorconfig
  17. .git-blame-ignore-revs
  18. .gitattributes
  19. .gitignore
  20. .gitmodules
  21. .gn
  22. .ignore
  23. analysis_options.yaml
  24. AUTHORS
  25. BUILD.gn
  26. CODE_OF_CONDUCT.md
  27. CONTRIBUTING.md
  28. fuchsia.code-workspace
  29. LICENSE
  30. OWNERS
  31. PATENTS
  32. pyproject.toml
  33. pyrightconfig.json
  34. README.md
  35. rustfmt.toml
  36. shac.star
  37. shac.textproto
README.md

Fuchsia

What is Fuchsia?

Fuchsia is an open source, general purpose operating system supporting modern 64-bit Intel and ARM processors.

We expect everyone interacting with our project to respect our code of conduct.

Read more about Fuchsia's principles.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See fuchsia.dev.