Description:
When persisting a SnipsNLUEngine object, the resources are copied to the destination path from the path where they were initially fetched. This is wrong as, once loaded, a SnipsNLUEngine instance should be self contained in memory, which means that deleting the underlying resources directory should not affect its behavior.
This PR fixes this by persisting the resources by serializing the resources objects that are loaded in memory. Each engine now owns its resources.
Checklist:
[x] My PR is ready for code review
[x] I have added some tests, if applicable, and run the whole test suite, including linting tests
[x] I have updated the documentation, if applicable
Description: When persisting a
SnipsNLUEngineobject, the resources are copied to the destination path from the path where they were initially fetched. This is wrong as, once loaded, aSnipsNLUEngineinstance should be self contained in memory, which means that deleting the underlying resources directory should not affect its behavior. This PR fixes this by persisting the resources by serializing the resources objects that are loaded in memory. Each engine now owns its resources.Checklist: