Implement node create indexValueProcessors htmlStripper

[ComLock]

Documented here: http://repo.enonic.com/public/com/enonic/xp/docs/6.15.4/docs-6.15.4-libdoc.zip!/module-node-RepoConnection.html#create

But according to @runarmyklebust not implemented yet.

Future example:

_indexConfig: {
  default: 'byType',
  configs: [{
    path: 'data.response.body',
    config: 'fulltext',
    indexValueProcessors: ['htmlStripper']
  }]
}

[vbradnitski]

@ComLock I'm not sure about provided example, which processor or processors would you expect in next case:

_indexConfig: {
  default: 'byType',
  configs: [{
    path: 'data.response.body',
    config: {
                        "decideByType": false,
                        "enabled": true,
                        "nGram": true,
                        "fulltext": true,
                        "includeInAllText": true,
                        "path": false,
                        "indexValueProcessors": ['processor1']
                    },
    indexValueProcessors: ['processor2']
  }]
}

@GlennRicaud what do you think?

[ComLock]

@vbradnitski I really don't know about indexValueProcessors. The fact there was one called 'htmlStripper' is something @runarmyklebust told me about.

[GlennRicaud]

From what I see the behaviour to set a custom index config is already implemented. Just not documented.

Instead of passing a string 'fulltext', you pass an object. For example for the equivalent of a fulltext with htmlStripper:

_indexConfig: {
  default: 'byType',
  configs: [{
    path: 'data.response.body',
    config:  {
      "decideByType": false,
       "enabled": true,
       "nGram": true,
       "fulltext": true,
       "includeInAllText": true,
       "path": false,
       "indexValueProcessors": ['htmlStripper']
    }
  }]
}

[GlennRicaud]

@ComLock Could you try. We will close this issue then