Custom context notation

For engineers Tracking SDKs
1

With the .NET tracker, and a custom context schema path using dot notation, we’re getting a ton of bad records with the following error message: "error: ECMA 262 regex “^iglu:[a-zA-Z0-9-.]+/[a-zA-Z0-9-]+/[a-zA-Z0-9-_]+/[0-9]±[0-9]±[0-9]+$” does not match input string “iglu:com.nordstrom/custom_event/jsonschema/1.0.0”

Should we (and the docs) be using hyphens 1-0-0, or should the tracker be updated to convert? Many of the non-JS tracker docs specify dot notation. I’m happy to create a GH issue if the docs are incorrect.

https://github.com/snowplow/snowplow/wiki/.net-tracker#411-custom-contexts

Thanks!

2

Hey @seanhall - you should be using hyphens for schema versions, e.g. 1-0-0. Can you open a ticket with links to any documentation using periods (1.0.0)?

3

Sure, is it more useful to open one issue on the main Snowplow project or separate issues on the trackers?

4

If it’s all in the documentation, then it’s likely in the snowplow/snowplow wiki? So a single ticket in there with all the refs would be ideal. Thanks @seanhall!