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

Create a class entry for implicitly defined UML classes #85

Closed
songyang-dev opened this issue Apr 22, 2022 · 3 comments
Closed

Create a class entry for implicitly defined UML classes #85

songyang-dev opened this issue Apr 22, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@songyang-dev
Copy link

Some plantuml code only has statements between UML classes like this

LiteralExp <|-- TemplateExp

The left-right members of the association are not explicitly stated as classes using the class keyword. It would be nice if the parsed json result from this tool treats this as an implicitly defined class. The json should have a class entry like this, in addition to the left-right entry.

"elements": [
        {
          "name": "LiteralExp",
          "title": "LiteralExp",
          "isAbstract": false,
          "members": [],
          "extends_": [],
          "implements_": [],
          "generics": [],
          "stereotypes": []
        },
]
@songyang-dev songyang-dev added the enhancement New feature or request label Apr 22, 2022
@Enteee
Copy link
Owner

Enteee commented Apr 22, 2022

If I understand you correct, you would like the parser to infer the existence of a class (LiteralExp) because of the simple fact that there exists a relationship between LiteralExp and TemplateExp. Thinking about it, this is a bit much logic for a parser and not really something I would like to implement in the core.

But you could implement this functionality yourself in a custom formatter.

Leaving this open for now, maybe I misunderstood you.

@songyang-dev
Copy link
Author

You understood me correctly. It's fine if you don't want to implement this. I wanted to bring this parser a bit more high-level.

@Enteee
Copy link
Owner

Enteee commented Apr 25, 2022

yeah I don't think I will implement that. Sorry. Feel free to ask questions if you need help building a formatter.

@Enteee Enteee closed this as completed Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants