User:Ch4zm/Maps Revamp/Package Reorg

Main: User:Ch4zm/Maps Revamp

lots of questions...

first: pretty settled on this, we'll make an orphan branch and start from scratch

next question is, should package be renamed.

• only thing that uses it is the api, (oh and the gollyx-backend-generator, dang)
• those are using requirements and pointing to a repo
• will swap out default branch so it's now the orphan branch, but still have tags pointing to commits, consistent all the way through
• api will have legacy functionality available
• gollyx-backend-generator should not need anything changed. that api should stay the same.

src/ directory:

• will have a legacy subdir

maps api functionality and import:

• maps lambda api will swap out "maps" import with "maps.legacy"
• legacy endpoints left alone
• new endpoints - how to differentiate? this is where we get some complicated questions

option 1: api endpoint can have /v2/ in them, and package is renamed to maps2

• we're updating the imports anyway, so...
• this might lead to greater expansion of the api - more parameters being fed to maps, not just size, asking for patterns vs map patterns

option 2: don't change the package name, don't add any /v2, just keep piling on new endpoints, everything before Hellmouth VI will use legacy submodule, everything VI and later will use modern stuff

• cut a new version 600
• this is the way