Strawberry Meeting #9 #1251
patrick91
started this conversation in
Meeting Notes
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Strawberry meeting #8
Date: September 14, 2021, at 16:30 UTC+1 (your timezone)
Discord: https://strawberry.rocks/discord
Welcome!
If you are joining the Strawberry Community Call, sign in below so we know who was here.
Agenda Items
strawberry.context
(@jkimbo) Add strawberry.context #1243Direction
General direction is to make strawberry a library with great DX and community, as stated here: https://strawberry.rocks/docs/general/why
Should we have batteries included?
Yes, for now. we can decided in future if we want to split the library. We are doing a good
job of not asking for all the dependencies by using optional reps and extras, we can keep doing
that. We'll see if having a lot of integration in our code base gets messy in future.
How opinionated?
We can be opinionated, but we can allow people to "break" conventions when they know all the tradeoffs or have different preferences.
Make documentation consistent and opinionated, but still having the core flexible enough.
We should try to reduce the number of breaking changes for internal things (if people rely on them).
v0.x helps with this as it "allows" us to change API when we need, for now :)
Django support - Pydantic
Exposing fields by passing a flag? or configuration option
DRF has
__all__
(this should be propagated to nested classes)Figure out if it makes sense to merge bits of the django integration for now.
After that we can see how to re-use parts of the integration with Pydantic.
v1.0 and new website
We might have a new website for version 1.0 (not sure when this will happen).
We should implement Search ASAP
To solidify for version 1:
Hacktober fest (local event in London?)
We should groom issues, making easier to find issues for new contributors
Talk with Django London to see if we can combine the event (in person)
Extensions
Issues for extensions might be a good first issue
See some ideas of extensions here: https://www.envelop.dev/plugins
strawberry.context
We discussed @jkimbo's suggestion of using ContextVar for strawberry.context, but
there is not a lot of benefit in using them (user can still use them manually if needed).
We'll move it to a discussion and see if we should revisit in future.
Actions
@patrick91 Run tests without installed dependencies
@patrick91 Check if we are caching deps
@patrick91 Send more stickers
Beta Was this translation helpful? Give feedback.
All reactions