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

fix: DocViewer doesn't support multi level include #3210

Open
AClerbois opened this issue Jan 19, 2025 · 1 comment
Open

fix: DocViewer doesn't support multi level include #3210

AClerbois opened this issue Jan 19, 2025 · 1 comment
Labels
status:blocked Any issue blocked by another v5 For the next major version

Comments

@AClerbois
Copy link
Contributor

🐛 Bug Report

I tried to include a document into another document where this document is also included.

💻 Repro or Code Sample

Branch : dev-v5

My operations were :

  • In the project, FluentUI.Demo.Client, I create a document NewA.md into the existing document MigrationColor.md.
    This one is already included into the MigrationVersion5.md

While the visionalisation, I get an error message : "The Component INCLUDE error"

If I include the NewA.md in the MigrationVersion5.md, the content is display.

🤔 Expected Behavior

Display the included file

😯 Current Behavior

Display an error

💁 Possible Solution

I put the document one level upper.

🔦 Context

In the branch dev-v5

🌍 Your Environment

  • OS & Device: Windows 11, Microsoft Laptop Studio 2
  • Browser : Microsoft Edge, Google Chrome, Mozilla FireFox
  • .NET and Fluent UI Blazor library Version : dev-v5
@microsoft-github-policy-service microsoft-github-policy-service bot added the triage New issue. Needs to be looked at label Jan 19, 2025
@dvoituron
Copy link
Collaborator

I know that recursive includes are not possible. It is not yet a necessary function. Especially since to do that you need to detect A->B->A include loops. And that's another story.

But all new PRs are welcome 😀

@vnbaaij vnbaaij added status:blocked Any issue blocked by another v5 For the next major version and removed triage New issue. Needs to be looked at labels Jan 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:blocked Any issue blocked by another v5 For the next major version
Projects
None yet
Development

No branches or pull requests

3 participants