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

[mini.doc] Support hiding fields marked as private/protected #668

Closed
2 tasks done
kristijanhusak opened this issue Jan 24, 2024 · 2 comments
Closed
2 tasks done

[mini.doc] Support hiding fields marked as private/protected #668

kristijanhusak opened this issue Jan 24, 2024 · 2 comments
Labels
feature-request Request for a feature to existing module mini.doc

Comments

@kristijanhusak
Copy link

kristijanhusak commented Jan 24, 2024

Contributing guidelines

Module(s)

mini.doc

Description

Hey,

I'm planning to replace lemmy-help with your mini.doc for API documentation on orgmode.

It works great so far, I just noticed one thing that is missing. Fields marked as private/protected are still generated.

Field can be marked private/protected like this:

---@field private _my_private_field integer
---@field protected _my_protected_field integer

There are also some examples on https://github.com/LuaLS/lua-language-server/wiki/Annotations#field and https://emmylua.github.io/annotations/field.html

This is how mini.doc generates one section on my docs:

                                                                       *OrgFile*
                                   `OrgFile`
Class ~
{OrgFile}
Fields ~
{category} `(string)` current file category name. By default it's only filename without extension unless defined differently via #+CATEGORY directive
{filename} `(string)` absolute path of the current file
{headlines} OrgHeadline[]
{is_archive_file} `(boolean)`
{private} _file File

And this is what lemmy-help does:

OrgFile                                                                *OrgFile*

    Fields: ~
        {category}         (string)         current file category name. By default it's only filename without extension unless defined differently via #+CATEGORY directive
        {filename}         (string)         absolute path of the current file
        {headlines}        (OrgHeadline[])
        {is_archive_file}  (boolean)

Any chance to get this added? Thanks!

@kristijanhusak kristijanhusak added the feature-request Request for a feature to existing module label Jan 24, 2024
@echasnovski
Copy link
Owner

Thanks for the suggestion!

Looks reasonable. It is also somewhat related to #666.

No guarantees on the timeframe, though.

@echasnovski
Copy link
Owner

As there have already been several suggestions which are more or less "make this LuaCATS annotation work", I think it is more reasonable to use #666 as a tracking issue. This will keep all suggestions easily skimmable. I've added this one here, so will close this issue.


Sorry, there are still no guarantees about when this is going to happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for a feature to existing module mini.doc
Projects
None yet
Development

No branches or pull requests

2 participants