Is marked rst feature working?

[MrChocolateMoose]

Overview

I am having extreme difficulty getting marked rst working.

I have a project set up that is working perfectly for oneline_needs, but then I try to have it discover marked rst and I have not been able to succeed on version 1.1.0.

I have set:

[codelinks.projects.my_project.analyse]
...
get_rst = true
...

I have tried about a half dozen different types and combinations of the inline marked rst.

The engine is successfully saying:

Marked rst extracted: 1..N (i.e. > 0)

Therefore, I know it is successfully reading the marked rst.

However, I don't know if there is further verbosity from there though on why they are not showing up under src-trace need.

Ideally the example here would show this feature working but it does not have get_rst = true.

Before I dive into more details on my exact project setup and trying to reproduce a minimal example, can you confirm it's working in the first place?

[MrChocolateMoose]

@juiwenchen @ubmarco

Any thoughts on this one? I don't mind providing more details, but I felt like it wasn't working in the first place

[ubmarco]

@juiwenchen That's your topic - my first shot would be to look whether this is tested. If not, this is a gap we need to close.

[juiwenchen]

Hi @MrChocolateMoose,

I have to admit, the documentation may be a bit confusing.

Currently, the directive src-trace only interacts with one-line needs, which is mentioned in the attention at the beginning of Directive

get_rst works only with CLI command analyse. Once it's enabled, Source Anaylse extract the metadata of the marked RST and export to a JSON file for the further uses.

It is in our roadmap for src-trace to support RST, but it's currently not ready yet. I will look into it and inform you once it's done