Alexandre Rafalovitch

> Purely responding to the URP response part, it’s definitely not possible for URP to send non-error responses. I do think its something we should implement though, since it will...

@noblepaul I don't think your proposal is fully thought out. 1. This seems not orthogonal to being able to send CSV/JSON/XML/DIH to it, if you are proposing for it to...

Reviewing leftover references: The /browse is still mentioned in the following files: - example/files/README.txt (actually that is broken even in released Solr) - solr/solr-ref-guide/src/solr-tutorial.adoc - solr/solr-ref-guide/src/initparams-in-solrconfig.adoc - solr/solr-ref-guide/src/rule-based-authorization-plugin.adoc Looks ok...

I am missing some of the skills to do that at the moment and my current focus is on Solr. :-( But perhaps after that.

That example is still uncompressed though, right? > "body": "basically what I want to do is forward people to a ...." I was thinking about: > 'what': doc1, doc2, doc3...

Oh, my mistake. I was looking at example_data.json instead of example_index.json. That's exactly what I was thinking about. Looks like the feature is implemented and maybe it just needs to...

I think Node.js or execjs is the best way to be DRY. And isn't SASS compilation already has a similar pipeline? This could be just 'index compilation' step in the...

This may have been fixed for the GitHub latest with fallback to the SolrField. Though this field may be more like LatLong in terms of specific treatment.

Thank you for reporting this. It's been quite a while since this code has been retested and there were a lot of changes in a meanwhile to Yeoman and Vagrant....