First-pass at some bulk-expanded story endpoints.#470
Open
lye wants to merge 1 commit into
Open
Conversation
Right now the chapters section is a bit bare -- there's not much metadata the backend service currently exposes for these. Will probably add the chapter rewards and locations (and maybe event metadata, if I have the courage to dig that out) as part of a future pull request. This also kindly omits the account side of things for exposing which chapters have been completed (which is on a per-character basis). This is a bit more finicky because the personal story is branching -- not entirely certain how to best express that. Finally, on a related note, the relations between chapters is currently pretty vague (e.g., that only one of the orders can be selected). Still need to figure out how to express that in a coherent way.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Right now the chapters section is a bit bare -- there's not much metadata
the backend service currently exposes for these. Will probably add the
chapter rewards and locations (and maybe event metadata, if I have the
courage to dig that out) as part of a future pull request.
This also kindly omits the account side of things for exposing which
chapters have been completed (which is on a per-character basis). This is
a bit more finicky because the personal story is branching -- not entirely
certain how to best express that.
Finally, on a related note, the relations between chapters is currently
pretty vague (e.g., that only one of the orders can be selected). Still
need to figure out how to express that in a coherent way.