garethj-msft/csdltodiagram

Simple console app and supporting library to generate PlantUML diagrams from an OData CSDL file.

csdltodiagram's Issues

Types in referenced files that are only referenced from operation parameters get missed from diagram.

Multiple namespaces should be supported.

Package CsdlToDiagram 0.14.1 is not compatible with net5.0 for vs2019

dotnet tool install -g CsdlToDiagram

error NU1202: Package CsdlToDiagram 0.14.1 is not compatible with net5.0 (.NETCoreApp,Version=v5.0) / any. Package CsdlToDiagram 0.14.1 supports: net6.0 (.NETCoreApp,Version=v6.0) / any
The tool package could not be restored.
Tool 'csdltodiagram' failed to install. This failure may have been caused by:

• You are attempting to install a preview release and did not use the --version option to specify the version.
• A package by this name was found, but it was not a .NET tool.
• The required NuGet feed cannot be accessed, perhaps because of an Internet connection problem.
• You mistyped the name of the tool.

For more reasons, including package naming enforcement, visit https://aka.ms/failure-installing-tool

Actions and functions are not supported

Id property is added to every entity instead of just ones with no base type.

Top-level Notes should be supported

There should be representations of various AGS attributes

AGS attributes should have visual representations
ags:IsMaster=true

Non-mastered entities should be visually distinguished

Note: comments on class members should be allowed.

Represent them with a leading period followed by two spaces.

e.g.
{field} -events: Collection(event) [0..]
. ISO8601 year. Must be unique within the tenant.
{field} -people: Collection(person) [0..]

There should be unit tests!

Or tests at any rate. Obviously. Visual inspection is far from ideal.

Optionality on a collection-valued navigation property should not be supported

Nullable=true means collection can CONTAIN nulls, which we NEVER want, not that the collection can BE null.
Remove the ability to generate the [0..1] suffix in this case.

There should be a representation or readonly and writeonly

Option in command-line to specify your own PlantUml URL

We shouldn't be sending internal design info to the public plant server.

Does the graph server for Agora respond to command-lines?

If so, add the ability to send there via command line.

exe should published as a dotnet tool.