Skip to content

Expand fragment input definition parser to work with nested types #7983

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

Closed
DeamonDev opened this issue Apr 23, 2025 · 0 comments · Fixed by #7985
Closed

Expand fragment input definition parser to work with nested types #7983

DeamonDev opened this issue Apr 23, 2025 · 0 comments · Fixed by #7985
Assignees
Labels

Comments

@DeamonDev
Copy link
Contributor

💥 Proposal

Currently the FragmentParameterTypingParser used for parsing fragment input definitions works only for types of depth at most one. By that I mean the naturally associated AST tree for the type definition has height at most one. I propose to expand this parser to work with arbitrary definitions. So for examply it will be able to parse types such as:

  • Map[List[String], Map[String, Float]] (depth = 2)
  • Map[String, Map[String, Map[String, Map[String, Float]]]] (depth = 4)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant