Improved Schema Field Naming

[bpepple]

For the most part it looks like the schema follows the field naming of Comic Vine (which makes sense), but it might make the package easier to use if it was a bit less verbose. For example in the IssueSchema, one of the fields is character_credits where it would probably be better to shorten it to characters. So in use it would be:

res = session.issue(189810)
for c in res.characters:
    print(f"{c.name}")

instead of

res = session.issue(189810)
for c in res.character_credits:
    print(f"{c.name}")

Just in the IssueSchema I'm thinking it might make sense to rename all the _credits fields and also rename some other fields like issue_number (drop the redundant prefix), possibly changing person_credits to creators, etc.

Anyway, before working on this further I wanted to get some feedback to see if it's worthwhile to pursue.

[Buried-In-Code]

yea, I definitely want to go through and update the schema's to make them a bit more friendly. My first pass was just to make it all worked.

As a starting point, I agree that we should change:

1. drop all _credits
2. issue_number to number
3. person_credits to creators

[bpepple]

One thing I did notice is the person_credits schema doesn't define the creators' roles for this issue, which makes sense since the documentation doesn't make any references to it either. Lucky, since the IssueSchema is using include meta option it can currently access by using issue.person_credits[0].role, but it probably needs to be defined better, which unfortunately means inspecting the json.

[Buried-In-Code]

While I use the API docs for working out what the endpoints are, I normally use postman and traverse the JSON to create the schemas and work out what the actual filter fields are.

Unfortunately Comicvine doesnt quite have a nice Schema/Docs setup as Metron.