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

Supports to nested inclusion deeper than 3 level #2584

Closed
4 tasks done
Jeff-Tian opened this issue Jul 4, 2023 · 0 comments
Closed
4 tasks done

Supports to nested inclusion deeper than 3 level #2584

Jeff-Tian opened this issue Jul 4, 2023 · 0 comments
Labels
bug: pending triage Maybe a bug, waiting for confirmation

Comments

@Jeff-Tian
Copy link
Contributor

Describe the bug

When the nested inclusion is deeper than 3 levels, the most nested included file wasn't included in the outer most file.

Reproduction

  • Create a nested inclusion deeper than three levels
  • Go to the outermost file
  • The deepest file's content won't show up

Expected behavior

The deepest file's content should show up

System Info

System:
    OS: macOS 13.4.1
    CPU: (10) x64 Apple M1 Pro
    Memory: 11.29 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.3.0 - ~/.nvm/versions/node/v18.3.0/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 8.11.0 - ~/.nvm/versions/node/v18.3.0/bin/npm
    pnpm: 8.6.5 - ~/.nvm/versions/node/v18.3.0/bin/pnpm
    Watchman: 2023.05.08.00 - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 114.0.5735.198
    Safari: 16.5.1

Additional context

No response

Validations

@Jeff-Tian Jeff-Tian added the bug: pending triage Maybe a bug, waiting for confirmation label Jul 4, 2023
@brc-dd brc-dd closed this as completed in e8074e6 Jul 5, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug: pending triage Maybe a bug, waiting for confirmation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant