Geoff Cox

Although inefficient, you can currently use a custom API endpoint to implement the special view logic and just specify this endpoint in an on_change doc.

Interesting, I don't believe I have seen this before. I think the easiest solution could be to just use `JSON.stringify()` when making the log call. @sc0ttdav3y did you want to...

@sc0ttdav3y any progress on this?

Great. Please let me know if you need help.

Agreed. PRs are welcome and I can help if you are interested in submitting a PR ;)

Well, I think the key to making this enhancement is that you need to worry about multiple instances of the services, e.g. ChangeListener and also need to account for services...

1. I think that sounds reasonable 2. I think as global parameters is a good place for now. It would be easy to change this in the future. 3. I...

Yes, the conditional logic [only works against the top level](https://github.com/redgeoff/spiegel/blob/eb31e148e92e3b62546e257308180f197ee798c6/src/on-changes.js#L208). I can think of two possible enhancements for this: 1. Enhance https://github.com/redgeoff/spiegel/blob/eb31e148e92e3b62546e257308180f197ee798c6/src/on-changes.js#L210 to use recursion to support nested properties 2....

Using mango selectors would be a cool idea, but the current design takes a [single _changes feed per database](https://github.com/redgeoff/spiegel/blob/eb31e148e92e3b62546e257308180f197ee798c6/src/process.js#L324) and then checks all on_change docs. In order to support mango...

Thanks, I think this can be fixed by including the full path to the images in the README.md and DESIGN.md files, e.g. https://raw.githubusercontent.com/redgeoff/spiegel/master/spiegel.svg @broerse would you like to submit a...