You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is meant to be exclusive - just for the core payload key-value pairs. The reason it gets confusing is that you can insert a TrackerPayload as the data component of a SelfDescribing json because it is really just a Map under the hood. We could probably clarify this by:
Renaming it to something more appropriate like NonEmptyStringMap
Removing the ability to pass this object directly into the SelfDescribingJson
Perhaps there is something around package visibility we should be toggling too...
This issue is broader than just TrackerPayload. I've changed the title to reflect that. We want to hide "private" parts of the code - in an internal namespace as suggested - to allow us greater flexibility in future for creating breaking changes. This change would also make the tracker easier to use with a better API.
mscwilson
changed the title
Discussion: hiding TrackerPayload from public view
Move internal components into their own namespace
Dec 6, 2021
It is meant to be exclusive - just for the core payload key-value pairs. The reason it gets confusing is that you can insert a TrackerPayload as the data component of a SelfDescribing json because it is really just a Map under the hood. We could probably clarify this by:
NonEmptyStringMap
SelfDescribingJson
Perhaps there is something around package visibility we should be toggling too...
cc/ @alexanderdean
The text was updated successfully, but these errors were encountered: