plantuml-server/.editorconfig

root = true

[*]
charset = utf-8
end_of_line = lf
insert_final_newline = true
indent_style = space
indent_size = 2
trim_trailing_whitespace = true

[*.java]
indent_size = 4

[*.md]
max_line_length = off
trim_trailing_whitespace = false

[*.puml]
insert_final_newline = false

[{Dockerfile,Dockerfile.*}]
indent_size = 4

[.vscode/*.json]
indent_size = 4
frontend 2.0: initial version - auto refresh function - light and dark theme - monaco editor (vscode) with "apex" as syntax highlighting language * apex seems to work quite fine (better than no highlighting) * future possibility: own plantuml language syntax support * future possibility: autocomplete (to much work but maybe partial) - implemented example for `!theme ...` - implemented example for `<&icon>` * future possibility: code validation - implemented example for `@start...` and `@end...`: * should be the first or last command * should be of the some type (e.g. `@startyaml` and @endyaml) * should be used exactly once per document/diagram - editor and preview is splitable into two windows like the "Extract window" functionality on (plantuml.com)[https://www.plantuml.com/plantuml] - multi index / multi paging diagram support - diagram can be displayed/rended as PNG, SVG, ASCII Art or PDF - Ctrl+s download the PlantUML Code as code file (diagram.puml) - Ctrl+, opens the settings and Esc closes the settings 2023-04-29 00:29:29 +02:00			`root = true`

			`[*]`
			`charset = utf-8`
			`end_of_line = lf`
			`insert_final_newline = true`
			`indent_style = space`
			`indent_size = 2`
			`trim_trailing_whitespace = true`

			`[*.java]`
			`indent_size = 4`

			`[*.md]`
			`max_line_length = off`
			`trim_trailing_whitespace = false`

			`[*.puml]`
			`insert_final_newline = false`
docker: use always latest Graphviz release This will change the Graphviz behaviour inside the docker container. Until now it was always a fixed Graphviz version inside the Dockerfile. With these changes the docker container will always use the latest Graphviz release if the version was not manually set via the docker build argument `GRAPHVIZ_VERSION`. If not set as build arg fetch latest version of Graphviz based on their release name by default. An alternative would be to use `tag_name`. Also, to avoid the overhead of getting all kinds of relase data, GitLabs GraphQL interface could be used. ```bash curl -s \ -H "Content-Type:application/json" \ -d '{"query": "{project(fullPath:\"graphviz/graphviz\"){releases(first:5,sort:RELEASED_AT_DESC){nodes{name}}}}"}' \ "https://gitlab.com/api/graphql" \ \| jq -r '.data.project.releases.nodes[].name' \| sort -V -r \| head -n 1 ``` In GraphQL the alternative to `name` would be `tagName`. 2023-05-05 17:38:28 +02:00
			`[{Dockerfile,Dockerfile.*}]`
			`indent_size = 4`
add import and export diagram - export diagram * add a diagram export dialog where you can choose the file name and download type (code, png, pdf, ...) * set default download type to code * open file save dialog via menu or Ctrl+S (or Meta+S for Mac) - import diagram * similar to [draw.io](https://app.diagrams.net) * open a PlantUML diagram image, use metat data to get diagram code and load this diagram (Note: meta data is currently only supported by PNG and SVG diagram files) * support drag&drop * add diagram import dialog - since three are now multiple options/action -> create a little editor menu - add documentation (including gif examples) 2023-05-14 09:13:05 +02:00
			`[.vscode/*.json]`
			`indent_size = 4`