Closed skalee closed 3 years ago
@skalee yes this is kind of a bug -- if we encoded the "type" and "modifications" keys as strings we won't have double colons.
Yes, it's caused by using symbols, not strings as hash keys. BTW perhaps the best option would be to stringify keys just before writing concepts to files. I need to think about it.
For example, 112-01-01:
Note that
:type:
and:modification:
field names start with a colon.