Internals restructure

[patrick91]

@BryceBeagle and I had an impromptu chat last Friday about restructuring the internals. Our current structure is a bit messy, and moving forwards we want to

Current structure

Proposed structure

we also have miro board with the structure, which should make it easier to read and navigate: https://miro.com/app/board/o9J_lKpif3E=/?moveToWidget=3074457357166650259&cot=14

This also takes into account @BryceBeagle's proposed re-architecture of the types and in general feels much more organised as a structure.

Note that this is not going to touch public api and imports. The idea is that public imports should be short and memorable

@BryceBeagle feel free to edit this and put more details, I wrote it quickly during a break 😊

Upvote & Fund

• We're using Polar.sh so you can upvote and help fund this issue.
• We receive the funding once the issue is completed & confirmed by you.
• Thank you in advance for helping prioritize & fund our backlog.

[scratchmex]

So far the structure seems very nice. I only have one question, why is the core module inside types? Should not be swapped? strawberry.core.types?

[BryceBeagle]

IIRC, these were supposed to be the "core" types of strawberry. The other things in the strawberry.types directory aren't things that go on the schema and were to be just related to typing (e.g. unset and private). I don't remember why there's both a strawberry.types.scalar and a strawberry.types.core.StrawberryScalar, though. Maybe @patrick91 does?