Hydration of values starting with colon

[martinklepsch]

When storing a map like {:body ":D"} this gets converted to a keyword during hydration even though it is intended to be a string.

Maybe encoding special values in tuples [:matchbox.core/keyword ":abc/world"] would be an option but I'm not sure how feasible this is.

[crisptrutski]

The default behaviour is pretty overboard on the magic, and others have also had trouble. Took the cowards approach of making this user configurable, see #75

Using an array (ie. JS objects which just happen to have numeric keys, in Firebase) may be a bit too heavy on bandwidth, object allocation on sync and/or break certain kinds of queryabiity, so definitely some trade offs.

Having a default strategy that doesn't just assimilate all the ":strings" would be welcome though - perhaps contribute a strategy? Hopefully the pattern I took is self obviously and pleasant enough.

Not sure how far you want to take the "tagged literal" vocabulary, this obviously extends to dates, symbols, characters and a whole bunch of other scalar values.

[crisptrutski]

And then theres still sets, queues, ordered maps, etc as another dimention