Comments (6)
Original comment by Mark Mikofski (Bitbucket: bwanamarko, GitHub: Unknown):
fixes #21 document packages and class folder almost
from matlabdomain.
Original comment by Mark Mikofski (Bitbucket: bwanamarko, GitHub: Unknown):
@cpher this fix let's you document (and autodoc) matlab packages and class folders, but the method signatures in the methods block of the classdef will still cause sphinx-build to crash b/c Pygments doesn't recognize them, so we'll have to match them via regex and ignore them since the docstrings are in the method's file
from matlabdomain.
Original comment by Mark Mikofski (Bitbucket: bwanamarko, GitHub: Unknown):
fixes #21 document packages and class folder almost
from matlabdomain.
Original comment by Mark Mikofski (Bitbucket: bwanamarko, GitHub: Unknown):
changeset 8f18a8f should fix this
from matlabdomain.
Original comment by Mark Mikofski (Bitbucket: bwanamarko, GitHub: Unknown):
closed accidentally when pulling from main upstream branch
from matlabdomain.
Original comment by cpher (Bitbucket: cpher, GitHub: cpher):
The commit which closed this issue doesn't appear to have been related to the issue.
A similar issue will occur when working with a class defined in an @myclass folder.
from matlabdomain.
Related Issues (20)
- Wrong function name in tokens when defined without parentheses and docstring HOT 2
- Question about parseing scripts and using automodule. HOT 3
- Error report: AttributeError: 'MatClass' object has no attribute 'path' HOT 3
- SyntaxError in Matlab.py HOT 5
- Extension error during build related to an mlapp file HOT 1
- Unexpected class attribute: 'Nontunable' HOT 1
- [Meta] Gathering interest in a "Framework :: Sphinx :: Domain" PyPi classifier HOT 1
- Feature request: show matlab class property dimensions, class, validators HOT 1
- Subfolders in class folders are inappropriately treated as class folders. HOT 10
- Parsing warning HOT 1
- Inquiry on features and documentation: scripts, citations, comments and parsing of existing docs HOT 1
- "Island" comments in the properties section causes parsing of a class to fail HOT 1
- Unexpected parse warning HOT 1
- Document abstract methods HOT 2
- Vague error when there is an empty @ClassFolder HOT 1
- Extension error when deplyoing with GitHub pages HOT 4
- Check if auto-linking feature works with classes in folders with the same name. HOT 3
- bug in auto-linking literal block detection
- documenter.generate() being called multiple times for module HOT 1
- can't link function short name if it matches module name HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from matlabdomain.