Add @semanticNonNull draft#49
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
gaps | 4d7594a | Jun 02 2026, 04:40 PM |
| - name: "Martin Bonnin" | ||
| email: "martin@apollographql.com" | ||
| githubUsername: "@martinbonnin" | ||
| sponsor: "@martinbonnin" |
There was a problem hiding this comment.
Ping @captbaritone, @itamark, feels like you should be here. Is it OK if I add you?
There was a problem hiding this comment.
@martinbonnin sponsors have to be part of @graphql/gaps-editors (in order to have write access on this repo). You are also able to be your own sponsor.
There was a problem hiding this comment.
Sounds good everything works for me. I'm down to merge this and we can add Jordan/Itamar later on if/when they want.
|
@magicmark can you see why Cloudflare workers build is not happy? |
magicmark
left a comment
magicmark
left a comment
There was a problem hiding this comment.
@martinbonnin would you mind running npm run build to make sure the spec is valid spec-md and the website will build?
(or if you wanna give a 🚢 this will happen automagically #34)
deploy previews might take a little longer, still wip here #40
|
|
|
Looks like that didn't work... digging into it |
2 participants
I currently use https://specs.apollo.dev/nullability/v0.4/#@semanticNonNull as reference but GAPs feel like a better place.
Also, contrary to
onError, I don't necessarily expect that@semanticNonNullmakes it to the main spec since it's mainly used for compatibility. Hence me opening that GAP. Let me know what you think!