Important note by Daniel
Please don’t do that last one, though. It’s not very helpful, and studies have shown that I am not in fact a poopy butt.
If you’re just hacking with TelemetryDeck, consider using a single word for your type. It’s easy to type, and as long as your app is not too big, it’s easy to find the signal type you’re looking for.
What many of our customers do (and we ourselves internally as well) is using a dot notation that represents the path of an action or event inside the app.
Here are some examples:
We recommend you don’t make the paths too specific or deeper than, say, 3 levels. Otherwise you’ll run into annoying mismatches when you move a feature around but can’t really rename the insight type to match.
If you want to distinguish between views, actions and events, or just views and actions, you can add that to the type, such as
InsightEditor.MetaEditor.actions.SaveInsight. However, I personally don’t get much value from that. Instead, I usually annotate types implicitly using grammar:
Don’t be afraid to play around a bit and find out what works best for you!