The canonical gem source for LiquiDoc, a ruby-based documentation parsing and rendering utility enabling advanced builds with Asciidoctor, Jekyll, Liquid, and semi-structured data files.
Now that #40 is implemented, object collisions are possible. I won't go into why I thought this would not be a problem, but it definitely is. One issue is multiple files of the same name being ingested from different paths, such as platform1/data/product.yml and `platform2/daata/product.yml.
This really means adding the token: property to DataSource and making sure that class always processes data file ingest entries. (Not using object: as the property name because that namespace may be better used for ingesting data objects in this action, as in #83, in which case you might want to ingest an object: by name and rename it with token:.
This fix should also incorporate error handling for configured collisions.
Now that #40 is implemented, object collisions are possible. I won't go into why I thought this would not be a problem, but it definitely is. One issue is multiple files of the same name being ingested from different paths, such as
platform1/data/product.ymland `platform2/daata/product.yml.This really means adding the
token:property to DataSource and making sure that class always processes data file ingest entries. (Not usingobject:as the property name because that namespace may be better used for ingesting data objects in this action, as in #83, in which case you might want to ingest anobject:by name and rename it withtoken:.This fix should also incorporate error handling for configured collisions.