Beautify JSON output of parse and converse OR implement new _id strategy about articulate HOT 2 CLOSED

Given the discussion of the Oct 30's standup. I'm currently overloading the _id field of ES with a UUID. According to @milutz overloading the _id is not desirable in the long term.

That's why we synced up with @malave one more time in the _id/name strategy he implemented in conveyor to use names rather than the _id.

He is manually constraining the name in the API by not allowing duplicate names of elements. According to Luis, this would require a search to ES before each insert to check that name is not taken already but is the only way to do it given that ES doesn't have a way to constrain a field to check uniqueness.

In conclusion, the path to follow with the language API is to stop overloading the _id field and start to check the uniqueness of the name before each insert. In this case, given that there could exist multiple agents, we should check that the name could be repeated in different agents, or even we could have the same intent name in different domains inside an agent.

from articulate.

Duplicate of #33

from articulate.