Darrel O'Pry

Next sets NODE_ENV to dev when running next dev. see: https://github.com/vercel/next.js/blob/3e81809df44e5c36a52abc89b46bc53f18b83695/packages/next/bin/next.ts#L87 If just running `next` you may need to pass it. I don't normally do this in testing. Did you...

I took a stab at it, but my branch had other build problems afterwards I wasn't able to resolve quickly. I'll try Dev when I get a chance to work...

@tsubik hey any thoughts on merging this? Anything someone else can do to help if you're too busy?

The test isn't failing. I'm just getting the traceback in the console... It's pretty straight forward setup. windows10/python3.10/bash. `python manage.py test example.tests.test_grapple.SettingsTest.test_query_single_setting_with_site_filter_clashing_port` ``` Creating test database for alias 'default'... System...

@paul-apacio do you have time or interest to wrap up this PR?

I'm quite confused by @register_streamfield_block. In my project, I have a bunch of custom block types. For each block, I've implemented the block and a resolver and then registered them...

I dug into this some more... using @register_streamfield_block seems to add a `blocks` property as well that will include all your graphql fields... It's serviceable as I can still access...

Actually, it seems like `blocks` is coming from the struct block base class, `grapple.types.streamfield.StructBlock`

@Leden I wanted to check in and see if you had any time or interest in finishing up this PR?

@easherma did the example from @IAmNatch, https://github.com/torchbox/wagtail-grapple/issues/33#issuecomment-597954453, help your resolve your issue?