improve definition of custom selector

as noted by @achambers in #14

> Maybe what the real change needed here is a better way to define custom selectors....At the moment you either use the defaults or override the jsonBlueprint property, which means you'd need to duplicate the current default selectors and add your new ones in.
> Maybe we can look at a way to say, I want the default selectors and also these other custom selectors.

Read issue #14 and trace how the plugin currently handles the jsonBlueprint property and its default selectors. Define how custom selectors should be combined with defaults, then confirm that the behavior supports adding selectors without duplicating the current defaults.

Written by the indexing model from the issue text.