D
David Rickey
Right now an intro is retrieved when requesting a range that includes the start of a book (e.g. Genesis 50:26-Exodus 1:1). But, using that same example, if I want to start with the intro to Exodus and show it alongside the first chapter, with just using the passages api there is no way to do this. I need to request the intro directly, and then also request the following separately.
It would be very nice if the intros were able to be fetched consistently via the passages api. This could be done a few ways, by using the start range as id
0
,
intro
, or something else. Intros have their own chapter id (e.g.
Exo.intro
), but simply cannot be used via the passages api. Similarly, a passage request cannot _end_ with an intro, though a use case for that is probably not very common.
Additionally, sometimes the intro simply isn't desired. In my example above I'm requesting only two verses. It's highly likely that I don't want to have an intro interjected in the middle of the range of verses I'm asking for. So it would be nice to be able to not always fetch the intro.
Specifically, the two features I'd like to have for the passages api are:
  • allow us to retrieve passages starting with the intro (should also allow ending with an intro if desired)
  • include a query parameter to optionally exclude intros for passages that span books
April 20, 2021