feat: Add ts-morph for query resolution of fragments

[torjusb]

Description

This change allows putting query fragments into queries, and have them be resolved before the query is executed.

Given this code:

const author = defineQuery(`{
  name,
}`);

const query = defineQuery(`
  *[_type == "article"]{
    "title": coalesce(select($lang == "es" => title.es, title.en), ""),
    author->${author},
  }`);

previously, the executed query would then be:

*[_type == "article"]{
    "title": coalesce(select($lang == "es" => title.es, title.en), ""),
    author->${author},
  }

which is invalid GROQ. The changes in this PR will ensure the interpolated string is resolved before executed, so the full GROQ query which is executed is:

*[_type == "article"]{
    "title": coalesce(select($lang == "es" => title.es, title.en), ""),
    author->{
     name,
    },
  }

The query will also resolve if the author is imported from a different file.

What to review

This PR changes to using ts-morph to extract, parse and resolve the queries. Most of the logic is the resolve-queries.ts file.

Testing

There didn't seem to be much of a testing facility set up for this project. But happy to try to set something up if desirable.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​react-dom@​16.9.8 ⏵ 16.9.25			+1
	react@​16.13.1 ⏵ 16.14.0	+1		+1	+1
	@​types/​react@​16.9.52 ⏵ 16.14.66			+1
	@​types/​vscode@​1.91.0 ⏵ 1.103.0			+1
	@​types/​node@​20.14.14 ⏵ 20.19.13	+1		+1	+1
	ts-morph@​26.0.0
	prettier@​2.1.2 ⏵ 3.6.2
	react-dom@​16.13.1 ⏵ 16.14.0
	groq-js@​1.12.0 ⏵ 1.17.3	+1		+1
	@​sanity/​client@​6.21.1 ⏵ 6.29.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		[email protected] has Obfuscated code. Confidence: 0.94 Location: Package overview From: package-lock.json → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report