Closed j-q-arnold closed 4 years ago
i don't think any of the above are an issue in practice. the diagram syntax allows you to specify which files are included, it solves the scale issue - you can either exclude or include files. are you dealing with so many files this is too much to handle?
Working with reslang
diagram
fromdiagrams.md
.models/file
command does not work. Should bemodels/file
instead of switching toDestinationAccount
and related resources from some other project. Or give the repo with the source for the extended example.includeAll
syntax confusing. The example usesfiles.reslang
, which looks like a source file reference, but the repo does not have a file by that name. Unclear whatfiles
means and unclear what the.reslang
suffix means. Suggest some other syntax that removes the confusion with path names.includeAll
, the actualmodels/file/diagrams.reslang
includes a lineall
in the/include
section. Please give details for the lines in the/include
and/includeAll
sections./exclude
. Seems to work on individual resources, but would be helpful to exclude an entire resource tree (and associated actions). I have a top-level resource with subresources and actions. I excluded the top level resource in one diagram, but the subresources and the actions were still included. MaybeName.*
orName::*
? Maybe even/excludeAll
and include individual resources (?)./exclude
limitations make that tedious.