On top of #252, this implements expanded metadata on rich results motivated by #253.
The latter will be rebased in case this gets merged and that would allow for more
clarity on how to maybe expand the api with a suitable extension point so that
similar use cases like #253 can be implemented cleanly out of tree.
@lilydjwg apologies for 5d908b34a60e43b2eb4a4f7bda2bd325996ecff3 and thanks for the fixes! I've not (yet) set up a full blown dev env for this project. :smile:
On top of #252, this implements expanded metadata on rich results motivated by #253.
The latter will be rebased in case this gets merged and that would allow for more clarity on how to maybe expand the api with a suitable extension point so that similar use cases like #253 can be implemented cleanly out of tree.