property defaults should be documented correctly, if number shown as number, etc.

[joeced]

Originally reported by: Mark Mikofski (Bitbucket: bwanamarko, GitHub: Unknown)

---

currently property default values are shown as unicode strings. that means a number has quotes, and if string then it has double quotes.

---

• Bitbucket: https://bitbucket.org/bwanamarko/sphinxcontrib-matlabdomain/issue/1

[joeced]

Original comment by Mark Mikofski (Bitbucket: bwanamarko, GitHub: Unknown):

---

add @property doc returns docstring

• use repr() instead of str(), since repr() precludes str()
• fix bug, arg in getter is name, not attr!
• begin separating modname module from basedir absolute path
• not passing!
• if fullpath passed to matlabify is None, return None
• fix bug 1st arg of super calls to getter should be classname, but were all MatModule since copied/pasted from there oops!
• add not to multiline docstring immediately before property assignment in property block should have colon after comment marker eg "%:"
• class property module returns path, needs fixing, currently returns absolute path including basedir
• delete shadow init method from MATLAB documenter
• set parent to None, if module is in top level of basedir, needs fixing, looks like it sets parent = None if fullpath == basedir, which is not correct, this would put everything into a single package, which might be desirable but is not the most general case, not sure, hmmmm
• delete ModuleAnalyzer debugging stuff
• delte objtypes, since same as python autodoc
• add set self.doc_as_attr = something to import_object for classes
• add MatModuleLevelDocumenter and MatClassLevelDocumenter classes

[joeced]

Original comment by Mark Mikofski (Bitbucket: bwanamarko, GitHub: Unknown):

---

the issue is that they are read in with their quotes if they are string literals, hence the double quotes.

Checking token types for primitive literals is fine, but for matlab arrays and more complicated property defaults, it could get tricky

proposal:

• if primitive literal, use tokens to resolve and recast as Python equivalent
• if some tricky matlab type, leave as string, or recast to python equivalent if possible
• leave as an <MatObject: "blah">