Add a hook to allow to exclude specific node

Hi @adelgado12

Interesting feature request.

I personally prefer the hook proposition to the field proposition, especially because the field proposition would store entities ids in the settings and those ids might not exist or be different when we work with multiples environments.

Hi @macsim

Good idea the hook proposition, i'm not sure event dispatcher is adpated because we can't see result on listener in process unlike hooks.

I changed the code to use a hook rather than the configuration field

Hi @adelgado

Sorry for the delay and thank you for the great job you've done here.
I merged your work on 2.0.x
Still need to port it on 3.1.x

I am finally going to revert the commit made on 2.0.x cause it still needs some work

• line 12 in index_now.api.php should be removed
• I didn't tested every use case before to merge (shame on me)
• For each entity type, we need to add a test that will cover the FALSE return on index_now_is_indexable_entity() function call (we'll check that the next function won't be call in those use cases). Those tests functions should be called test[ENTITY_TYPE]ExcludedByHook()