-
Notifications
You must be signed in to change notification settings - Fork 16
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
Symptoms task still unchecked in README's todo #64
Comments
We mean the symptoms of the individual diseases. The output for the symptoms is not an array yet. |
Okay, understand it better now, will see if it's something I could do. |
Awesome. Looking forward to your contribution.
On Mon, 22 Oct 2018 at 7:50 PM, Okoko Michaels ***@***.***> wrote:
Okay, understand it better now, will see if it's something I could do.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#64 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHSs3khDUcGkIkEKsvgEMnpZjGBiFTlDks5unhOFgaJpZM4Xssp_>
.
--
Osioke (O-sho-keh) "Sprime" Itseuwa
Product Analyst and Manager.
*I designed and managed the development of Disease Info
<https://disease-info.herokuapp.com/>. It is a web app helping to reduce
deaths by preventable and curable diseases, by making disease information
easily accessible. You can read the story here
<https://blog.devcenter.co/disease-info-the-story-so-far-a476a576e3cf#.wch9adk4f>.*
*I did a brief study on the informal market in Nigeria and how Fintechs can
improve it. You can read the research essay here
<https://spracks.com/enabling-the-nigerian-informal-sector-with-financial-services-7d1f6df7831f>.*
*"If you give to life, life will surely give back to you.."You've just been
sprimed <https://sprimed.com/>.*
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tested out the API url here and it seems to be returning the disease symptoms just fine. But then, it's still unchecked as an item in the todo list in the project's readme. Is there an issue with the current implementation or the readme is just out of sync? :)
The text was updated successfully, but these errors were encountered: