Skip to content
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

feat: Multiple translations #60

Open
2 tasks
JustinhSE opened this issue Nov 8, 2024 · 5 comments
Open
2 tasks

feat: Multiple translations #60

JustinhSE opened this issue Nov 8, 2024 · 5 comments
Labels

Comments

@JustinhSE
Copy link
Collaborator

Overview:

We need to integrate multiple Bible translations into our application. Currently, we only have the KJV version available. To enhance user experience, we need the following feature:

  • Multiple Translations: Allow users to compare verses across different Bible translations.

Tasks:

  • Research and Identify API: Find an API that provides access to multiple Bible translations and supports the features mentioned above.
    Integration: Integrate the selected API into our application to enable the display of different Bible translations
  • Add a button next to the results to convert the scriptures into the user's selected version only if it can be found
@JustinhSE JustinhSE changed the title fix: Investigate and Resolve Slow Fetching from Backend API bug: Investigate and Resolve Slow Fetching from Backend API Nov 8, 2024
@JustinhSE JustinhSE added bug Something isn't working Backend 🛠️ labels Nov 8, 2024
@JustinhSE JustinhSE changed the title bug: Investigate and Resolve Slow Fetching from Backend API feat: Multiple translations Nov 8, 2024
@JustinhSE JustinhSE added Enhancement 🚀 New feature or request good first issue Good for newcomers and removed bug Something isn't working labels Nov 8, 2024
@ciaracade
Copy link
Contributor

I'd like to take this!

@JustinhSE
Copy link
Collaborator Author

@ciaracade i am going to delay this issue for a few days unfortunately as in #41 we are thinking about storing verses in a different way. Would rather give you standardized return params from our conclusions to help with your potential usage of an api.

@ciaracade
Copy link
Contributor

Sounds good :)

@JustinhSE JustinhSE added the Hold For the issues that should not be worked on righ now label Nov 19, 2024
@JustinhSE
Copy link
Collaborator Author

#56 is almost done, just need the front end to receive the endpoint correctly and then you can take this issue @ciaracade

@JustinhSE JustinhSE mentioned this issue Nov 25, 2024
6 tasks
@JustinhSE JustinhSE removed the Hold For the issues that should not be worked on righ now label Dec 6, 2024
@JustinhSE
Copy link
Collaborator Author

JustinhSE commented Dec 6, 2024

For any contributors, use the same Youversion API in #61 as it has the most commonly used version

AMP 
KJV 
NIV 
NLT

@JustinhSE JustinhSE removed the good first issue Good for newcomers label Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants