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

Relative paths cannot be included recursively #716

Open
alexander-skoblikov opened this issue Jun 5, 2024 · 1 comment
Open

Relative paths cannot be included recursively #716

alexander-skoblikov opened this issue Jun 5, 2024 · 1 comment

Comments

@alexander-skoblikov
Copy link

alexander-skoblikov commented Jun 5, 2024

Describe the bug
we use several repositories with the following structure

  • a common repository that contains several modules with the basic gql schemas
  • service repositories that extend and reuse the basic gql schemas

In the current plugin version, if the link to a common repository is specified in glob format - common schemas will not be included recursively.
But it works if you specify a link to the schema file directly.

To Reproduce
I created a repository that simulates the project structure
https://github.com/alexander-skoblikov/graphql-intellij-plugin-relative-recursive-path

Expected behavior
models are imported recursively and are available in the service repository, as in the case when the path to the scheme is specified explicitly
image

Actual behavior
models are not imported recursively and are not available in services repositories
image

Version and Environment Details
Operation system: MacOS Ventura 13.6.4
IDE name and version: IntelliJ IDEA 2024.1.2 Build #IU-241.17011.79, built on May 22, 2024
Plugin version: 241.14494.150

@vepanimas
Copy link
Collaborator

vepanimas commented Jul 15, 2024

Specifying a path to a single file that is out of the current module scope is supported, though is not recommended. It's mostly a hack for some specific scenarios the users reported before. The same for glob patterns is not supported. Overall, we aim to align our plugin's functionality with the graphql-config library. It explicitly requires creating a single configuration file for monorepos, with sub-projects configured using the projects key. More info is available in our docs and in the graphql-config docs.

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