If a user of signals was to add custom Core Data models to their database outside of what was generated by the schema, they would be overwritten and cleared out every time signals is ran.
A first pass would be to detect this and warn the user their custom core data model is about to be cleared and that they should keep their custom core data objects in a separate core data store.
We implement some logic to check for their custom core data objects and re-include them in he core data xml that we generate.
Potentially this could also be solved if we were to implement #19
If a user of signals was to add custom Core Data models to their database outside of what was generated by the schema, they would be overwritten and cleared out every time signals is ran.