Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maybe: Relax 'label' requirement for deferred named fragments #3256

Closed
Tracked by #3093
calvincestari opened this issue Oct 17, 2023 · 0 comments
Closed
Tracked by #3093

Maybe: Relax 'label' requirement for deferred named fragments #3256

calvincestari opened this issue Oct 17, 2023 · 0 comments

Comments

@calvincestari
Copy link
Member

calvincestari commented Oct 17, 2023

The label is required for naming purposes on deferred inline fragments however for named fragments we already have been given something to name it. It's still unknown whether the label will be required for execution.

The work here is to relax the requirement for a 'label' argument on deferred named fragments only, and only once execution of deferred fragments has been implemented so we're sure it's absolutely not needed.

@calvincestari calvincestari added this to the `@defer` support milestone Apr 5, 2024
@AnthonyMDev AnthonyMDev closed this as not planned Won't fix, can't repro, duplicate, stale Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants