-
Notifications
You must be signed in to change notification settings - Fork 70
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
Can the JSON serialisation of ontologies be ordered in some way? #447
Comments
I guess this would have to be fixed in the API: https://github.com/geneontology/obographs |
Thanks Jim. @rctauber better to ticket there? |
No, I'm responsible for this, tempted to rewrite as scala as I hate all the java boilerplate |
btw think this is high priority, spurious diffs in git are evil |
Should we move this to obographs or would you prefer to keep the issue open here @cmungall ? |
Should definitely be moved to the obographs repo
…On Thu, Mar 21, 2019 at 6:57 AM Rebecca Tauber ***@***.***> wrote:
Should we move this to obographs or would you prefer to keep the issue
open here @cmungall <https://github.com/cmungall> ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#447 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AADGOY9u1lIxtZHBAozJoasS2wWWMqQfks5vY4-_gaJpZM4bcw_8>
.
|
Migrated to geneontology/obographs#42 |
So that GitHub diff is not confused every time we make a new release involving json serialisation of our ontologies. Low priority, but would be greatly appreciated!
The text was updated successfully, but these errors were encountered: