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.

Sign up for GitHub

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

Jump to bottom

Fixing poor docstring formatting for @callback #2728

Closed
wants to merge 4 commits into from
Closed

Fixing poor docstring formatting for @callback #2728

wants to merge 4 commits into from

Commits on Jan 21, 2024

  1. 🎎 Removed the nested feature list which was causing the formatting is… 

    …sues. Replaced it with a heading for the section and paragraph separated portions for each function parameter.
    @woefulpines
    woefulpines committed Jan 21, 2024
    Configuration menu
    Copy the full SHA
    b3a0386 View commit details
    Browse the repository at this point in the history

  2. 🎎 Fixed the formatting in regards to sublist within param manager wit… 

    …hin the parameter list.
    @woefulpines
    woefulpines committed Jan 21, 2024
    Configuration menu
    Copy the full SHA
    4ccda3f View commit details
    Browse the repository at this point in the history

  3. 🎎 Fixed the linters error by replacing empty lines with newline chara… 

    …cters at the end of each keyword subsection.
    @woefulpines
    woefulpines committed Jan 21, 2024
    Configuration menu
    Copy the full SHA
    e88697e View commit details
    Browse the repository at this point in the history

Commits on Jan 28, 2024

  1. 🎎 Reintroduced feature lists with newline character breaks for readib… 

    …ility while avoiding linter blank line errors.
    @woefulpines
    woefulpines committed Jan 28, 2024
    Configuration menu
    Copy the full SHA
    35c83bb View commit details
    Browse the repository at this point in the history