As bundles emerge as the central organizing pattern for Aquameta modules, it's becoming clear that a very common pattern is to reference a row by its bundle name, plus "name", whatever that might be. We do this with widgets already on import, referencing {namespace}:{widget.name} and have a custom function for resolving them. Other places do crude hacks around this missing functionality as well.
It would be nice to be able to do this generically with all manner of other things, for example documentation. A bundle's documentation should be able to link to sub-pages just by referencing them by name, but since multiple bundles may contain documents with the same name -- unique to the bundle but not globally -- it's the same pattern as widget. There are other examples too.
So, create something akin to a "bundle_row_id" which should contain:
bundle name (or id...hmm)
text_id_column_id -- the column that contains the human-readable identifier for the row
text id -- not the field's pk but rather it's text identifier
As bundles emerge as the central organizing pattern for Aquameta modules, it's becoming clear that a very common pattern is to reference a row by its bundle name, plus "name", whatever that might be. We do this with widgets already on import, referencing
{namespace}:{widget.name}and have a custom function for resolving them. Other places do crude hacks around this missing functionality as well.It would be nice to be able to do this generically with all manner of other things, for example documentation. A bundle's documentation should be able to link to sub-pages just by referencing them by name, but since multiple bundles may contain documents with the same name -- unique to the bundle but not globally -- it's the same pattern as widget. There are other examples too.
So, create something akin to a "bundle_row_id" which should contain: