-
Notifications
You must be signed in to change notification settings - Fork 3
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
Replace NaN
in protein metadata
#110
Comments
I changed the frontend to use JSON5 so that it won't fail to parse JSON strings from the API when they include To fully take advantage of this, everywhere the frontend detect |
Agreed. My temporary solution is also essentially converting |
Is it always |
Fairly certain it's |
If you know which collections/fields this is limited to, I can check for NaN where needed on the frontend. Then it won't be so important to fix this in the database. |
|
This is now fully handled in the frontend.
As a result, we no longer need to fix this in the backend. Going forward, if the backend needs to communicate |
Awesome! Thank you! |
Example:
https://testapi.datanator.info/proteins/meta/meta_combo/?uniprot_id=P37173
The text was updated successfully, but these errors were encountered: