You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The intents.json-file in each flow, containing an array with each intent as json, stores the intents in randomized order (completely changing the file each clone/pull).
This does not happen to any other file/array, like in the chats.json.
Theres no reason for that, especially when the intents in cognigy-ui are shown in alphabetical order.
This could be fixed by sorting the intents by name in the flow.js with something like this:
However its probably better to find out why CognigyClient.exportIntents shuffles around the intents every pull and fix it there?
Motivation:
Randomized intent-files are a problem, as we're trying to create changelogs for botprojects using cognigy-cli+git and git can't handle the changes in intents if they're randomized each pull.
The text was updated successfully, but these errors were encountered:
I just created a pull request that concerns this issue - although I went the route of your suggestion and added sorting to intents, flow config, lexicon csv and endpoints config #39
The intents.json-file in each flow, containing an array with each intent as json, stores the intents in randomized order (completely changing the file each clone/pull).
This does not happen to any other file/array, like in the chats.json.
Theres no reason for that, especially when the intents in cognigy-ui are shown in alphabetical order.
This could be fixed by sorting the intents by name in the flow.js with something like this:
However its probably better to find out why CognigyClient.exportIntents shuffles around the intents every pull and fix it there?
Motivation:
Randomized intent-files are a problem, as we're trying to create changelogs for botprojects using cognigy-cli+git and git can't handle the changes in intents if they're randomized each pull.
The text was updated successfully, but these errors were encountered: