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

Rendering structurizr graphic with includes fails #11

Open
Ka55i0peia opened this issue Feb 13, 2023 · 0 comments · May be fixed by #22
Open

Rendering structurizr graphic with includes fails #11

Ka55i0peia opened this issue Feb 13, 2023 · 0 comments · May be fixed by #22

Comments

@Ka55i0peia
Copy link

Ka55i0peia commented Feb 13, 2023

Watching the payload of sphinx->kroki and a quick view into the (nice) code (btw) leads me to create this issue

In structurizr dsl it is possible to spread a complex graphic/model into separate file using an include.

.. kroki::
   :type: structurizr
   :filename: workspace.dsl
   :options:
      view-key: some-view

with a workspace.dsl like this

!include some_file.dsl

workspace {
    //...
}

Rendering this graphic causes kroki server to fail with

java.lang.RuntimeException: some_file.dsl could not be found

This error message is correct, since the payload of the graphic contains only the workspace.dsl (not the included file).


By now in my eyes two paths are not worse to investigate further:

  • send several files to kroki
  • do the code embedding on sphinx-contrib/kroki side and send as one payload object (nothing more magic seams to be done by the include statement in structurizr dsl)

Does someone (maybe @hason as author, @pypamart as contributer) has a feeling about one over the other?

@Ka55i0peia Ka55i0peia changed the title Rendering structurizr graphic with includes Rendering structurizr graphic with includes fails Feb 13, 2023
@willson556 willson556 linked a pull request Feb 8, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant