Extend CLI functions

[o-muzyka]

Description

Extend SAMM CLI with new functions + test coverage:

• prettyprint: Format Aspect Model files
• to_java: Generate Java classes from Aspect Models
• to_asyncapi: Generate AsyncAPI specifications
• to_jsonld: Generate JSON-LD representations
• to_sql: Generate SQL scripts for Aspect data
• to_aas: Generate Asset Administration Shell templates
• edit_move: Move model elements between files/namespaces
• edit_newversion: Create new versions of models
• usage: Show where model elements are used
• aas_to_aspect: Convert AAS templates to Aspect Models
• aas_list: List submodel templates in AAS files
• package_import: Import namespace packages
• package_export: Export models as namespace packages

• Add support for repeated parameters (lists in kwargs)

Type of change

• New feature (non-breaking change which adds functionality)

Checklist:

• I My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works

[Hanna-Shalamitskaya-EPAM]

Let's add a test for incorrect command_type

[Hanna-Shalamitskaya-EPAM]

This test also can be move to the functional testing suitre

[o-muzyka]

I wanted to clarify the type of tests I’ve written. The current tests are unit tests, not functional tests.

• They target small helper methods like _format_argument and _process_kwargs.
• All external dependencies are mocked (e.g., subprocess, _get_client_path), so the tests run in isolation.
• Each test verifies only the logic of a single method and its return value.

By contrast, functional tests usually check a business scenario end-to-end, often without mocking, to ensure multiple components work together (e.g., calling the real CLI command and verifying the actual output).

Because these tests focus on isolated pieces of code, they fit the definition of unit tests.

➡️ My opinion is that we can simply keep them as part of our unit tests. There’s nothing wrong if I additionally tested a function more thoroughly — it’s not redundant, and having extra unit coverage will only help us.

Could you share your thoughts on this?

[atextor]

The Aspect should have the same name as the file

[o-muzyka]

I’ve renamed it to SampleAspect.ttl