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

The usage of scan_dirs is incorrectly documented #263

Open
james-d-mitchell opened this issue Feb 4, 2022 · 6 comments
Open

The usage of scan_dirs is incorrectly documented #263

james-d-mitchell opened this issue Feb 4, 2022 · 6 comments

Comments

@james-d-mitchell
Copy link

Thanks for the great project, I'm just starting to use this in the Semigroups package.

From the manual it seems like it should be possible to include a scan_dirs component in the gapdoc record passed to AutoDoc:

#! <Mark><A>scan_dirs</A></Mark>

AutoDoc( rec( gapdoc := rec( scan_dirs := [ "package_sources" ] ) ) );

But this doesn't work (I mean that the directory is not scanned). This only seems to work when scan_dirs is in the autodoc component.

@fingolfin
Copy link
Member

The code is there and it used to work for sure: all .g .gd and .gi files should be found. Huh

@james-d-mitchell
Copy link
Author

I release I haven't posted a minimal failing example, I'll try to come up with one and post that.

@fingolfin
Copy link
Member

Don't worry about that. I'll try to reproduce it tomorrow. Either it'll work for me on some package (then we can compare what's different to your setup), or I'll quickly repro the issue.

@fingolfin
Copy link
Member

(I mean, of course if you post something, that'll probably be helpful; but as it is, I think you report is sufficient to look into this; it's mostly a matter of finding the time).

@fingolfin
Copy link
Member

Just to avoid a misunderstanding: the two scan_dirs have different jobs, one scans for autodoc comments, the other scans for GAPDoc comments

@fingolfin
Copy link
Member

@james-d-mitchell I should point out that recog uses this option successfully in both the gapdoc and the autodoc record.

So at this point I am at a loss what exactly the problem is you observed. I need more details, otherwise there is nothing I can do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants