This is to facillitate ease of implementing #1406. (Tags for messages could then be added dynamically) Ultimately once we make the router support hiearchical routing, (#770) we can then remove the name field and just the parse info for tags from that. Until then, we can parse the tag name as `fmt.Sprintf("%s %s", msg.Type(), msg.Name())` |
||
|---|---|---|
| .. | ||
| app1.go | ||
| app2_test.go | ||
| app2.go | ||
| app3.go | ||
| app4_test.go | ||
| app4.go | ||