BamaCharanChhandogi / Diabetes-Prediction

This website provides a platform for users to predict their likelihood of developing diabetes based on various factors.
https://diabetes-prediction-gamma.vercel.app/
MIT License
15 stars 39 forks source link

Fixed hero section #118

Closed Utsavladia closed 1 day ago

Utsavladia commented 1 week ago

115

Fixed hero section for both mobile as well as large screeen sizes...

image image

vercel[bot] commented 1 week ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
diabetes-prediction ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 3, 2024 4:18am
BamaCharanChhandogi commented 1 week ago

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

Utsavladia commented 1 week ago

@BamaCharanChhandogi I removed the changes of package.lock.json and Made it responsive although the reposive was needed for navbar not hero section still i fixed it...

image

BamaCharanChhandogi commented 1 week ago

The navbar code is perfect when I reload the site extra space showing. please fix it.

image

Utsavladia commented 1 week ago

@BamaCharanChhandogi I have fixed it... The problem is little bit related to late rendering of the GotoTop button at the bottom right

https://github.com/BamaCharanChhandogi/Diabetes-Prediction/assets/124615886/b6639db9-8d11-4f1f-9f59-a394ee44b020

BamaCharanChhandogi commented 2 days ago

Fix Merge Conflicts then I can merge.

Utsavladia commented 1 day ago

@BamaCharanChhandogi fixed

BamaCharanChhandogi commented 1 day ago

It still has not fixed that bug. Now, after changes giving new errors in the console. I am closing this PR. See you in the new issue/PR. Thanks.

image

Utsavladia commented 1 day ago

@BamaCharanChhandogi This is because of the new chagnes made in main branch after this PR. should i create a new PR on this issue with the changes based on latest branch to avoid new errors....?