Provide better documentation about RDF export options

[tonyKunchev]

There are some specifics in the RDF export command that aren't described well enough.

For example: the user is able to provide -q, --sparql and -m, --mapping within a single command, but there is no mention what would happen, which option will be used.

[VladimirAlexiev]

Tony:

-q will take precedence over -m

I've added this to https://github.com/Ontotext-AD/ontorefine-cli/blob/main/commands/rdf.md.
But @tonyKunchev how do you specify the project? is it in the -u url?

[tonyKunchev]

Hi @VladimirAlexiev,
please when you are adding something to the codebase, go through proper merge request.
Pushing directly into the master/main branch isn't a good practice.
You've broke tests with your change and probably ignored the notification emails.

The change should be added as documentation for the command so that when the someone writes cli rdf --help it provides that information. That is why I've submitted this issue.

Regarding the question for the project, it is provided as required parameter to the commands, not named argument.
For example cli rdf 1234567890 -q query.ru -u http://localhost:7333 ......

[VladimirAlexiev]

@tonyKunchev
How did I break tests by changing a .md file?

[tonyKunchev]

The tests are using the .md files to ensure that same is returned, when ontorefine-cli <command> --help is executed.
So by changing the file without updating the documentation in the code for the command, breaks the tests.

There is a CI process for that reason and that's why every change should go through merge/pull request.

[VladimirAlexiev]

I think rather than forcing the developer to copy some text in two places, you should have a part of the CI to do that copying.
Cheers!

[tonyKunchev]

That is actually wrong.
We should NOT automatically copy-paste things from the documentation into the source code.
What will happen, if someone updates the documentation, describing something that isn't implemented?

The flow is: implementation -> command documentation -> repository documentation, not the other way around.