autoDocstring icon indicating copy to clipboard operation
autoDocstring copied to clipboard

VSCode extension that generates docstrings for python files

Results 102 autoDocstring issues
Sort by recently updated
recently updated
newest added

**Describe the bug** When I generate a Google Style Docstring inside a function there are four trailing whitespaces after the three closing quotes, here they are marked with asterisks: ```...

bug

**Describe the bug** When creating a module docstring for a `.py` file, it is created an extra indent. **Versions (please complete the following information):** - autoDocstring Version: v0.5.3 - Operating...

bug

Extension does not seem to be working when the Python code is in a code cell in a Jupyter Notebook. Extensions for the files are `.ipynb`. autoDocstring version is 0.5.4

**Describe the bug** When creating a docstring, function parameters, their types and the return-type is not taken into consideration. The generated docstring will only contain a seemingly random selection of...

bug

Current functionality will add Exceptions for lines that are prefixed with `raise`. It would be good to have the docstrings to include any lines that are prefixed with `assert` also....

bug

The feature of creating a separate mustache.js file creates an unnecessary overhead in my opinion. Toggleable variables in the VSC settings.json for each section could be a lot cleaner and...

feature request

**Describe the bug** After an upgrade to v0.5.3, when I try to create doc strings I get the error: `command 'autoDocstring.generateDocstring' not found`. I tried uninstalling and reinstalling the latest...

bug

**Describe the bug** autoDocstring fails to generate any docstrings a MacBook Pro 2017 with BigSur 11.2.2 with ENOENT error: ``` AutoDocstring encountered an error. Please view details in the 'autoDocstring'...

bug

**Describe the bug** The following situation where you have a quoted type hint for the return leads to args to be skipped and return type is not guessed correctly. It's...

bug

**Describe the bug** Comments in multi-line function signature get parsed and added in docstrings, instead of being escaped. It seems to relate to *commas* inside comments, as `# a comment...

bug