-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make import of NMLs more resilient #4374
Comments
NML for reference: Timestamps also seem to differ in various NML importer/exporters out there. Perhaps we can ignore those on import when they don't match. Or replace them with the current time etc. |
Related to #4396. |
Let's do it in front-end first. |
Frontend is done and merged. |
The knossos-generated NML is accepted by our back-end parser. It also handles unnamed trees. So I suppose the only thing left there is splitting unconnected-component-trees. This should replace |
To make it easier to switch from Knossos to WK, the import of NMLs should support:
<things>
without names (can default to "Unnamed tree 1" or similar) (already supported by the backend)Might need to happen in front-end in back-end.
The text was updated successfully, but these errors were encountered: