Generate types as separate files

[Serhioromano]

I tested your IDe. What I create a type it adds it to JSON file. That is strange. We have a syntax for that. I think the file should have been created with content

TYPE MyType: STRUCT
    x1:BOOL;
END_STRUCT
END_TYPE

Why is it important

If anytime the AI will be trained to program ST language, it will require additional explanations that types are JSON structure for this IDE only. That is not good approach. That can cut this IDE off the new technologies or require development of additional tools like MCP server.

Another reason is code transfer. If I have struct or enum defined in Codesys for example. It would be easy just copy\paste transfer it to new IDE. In current setup it will require manually to recreate all types.

Another reason, if we add code navigation, like "Go to definition" where will it go? If there is a tool that can parse ST files and create a tree, how those types will be parsed as part of ST language parser (LSP)? And when click on type it should open file with exact place there TYPE definition starts.

[thiagoralves]

Could you add this as an issue please? We are not tracking GitHub discussions so I’m afraid it will get lost here. Thanks!