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

Multiple Ranges #14

Open
logoscreative opened this issue May 29, 2016 · 6 comments
Open

Multiple Ranges #14

logoscreative opened this issue May 29, 2016 · 6 comments
Labels

Comments

@logoscreative
Copy link

I've run into a little trouble with multiple chapter:verse ranges. Some examples:

  • Prov. 23:19-21,29-24:2
  • Psalms 63:1-11,Psalms 98
  • Psalms 138,139:1-17,18-23

I have access over the way this data is formatted before making the call, but I haven't totally been able to figure out what a correct or working format is. Any tips?

@seven1m
Copy link
Owner

seven1m commented Apr 29, 2017

http://bible-api.com/proverbs+23:19-21,23:29-24:2 (including the chapter again) fixes the first one.

The other two are tricky and I'm not sure what's going on. Might be a bug in our bible_ref library.

@seven1m
Copy link
Owner

seven1m commented Apr 29, 2017

Oh, and by the way, sorry for the nearly year-late response on this one. 😬

@logoscreative
Copy link
Author

@seven1m No worries. Any way I can help with the other examples?

@seven1m
Copy link
Owner

seven1m commented May 24, 2017

@logoscreative I fixed one of these cases:

@seven1m
Copy link
Owner

seven1m commented May 24, 2017

I'll poke at the other ones soon...

@jmichae3
Copy link

jmichae3 commented Aug 9, 2017

Technically, book and chapter changes in a list are separated with ; not , butnot with chapter lists which are separated with comma.

Example: 1jn 5:7,8;philippians 4:8-9;james 4:7;psalms 103,
This is consistent with method=GET.

@seven1m seven1m added the bug label Jul 6, 2020
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

3 participants