You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've written a epydoc to define new field in the following way. But Unknown Field errors occur if I run pydoctor on my project. I think it's because current version of pydoctor do not support newfield for reStructuredText. Is there any other mechanism for defining new field? Or do you have any plans to update?
There is currently no way of defining custom fields.
Adding the newfield mechanism seems possible, though. Maybe we should not bother with plural handling (like epydoc) and provide simpler syntax, like: :newfield tag: label
Regarding implementation, we should add a new method: handled_newfield to the FieldHandler:
This method should dynamically patch self in order to add the required handle_<newfield> method. This method could simply add the new field content into a self.newfields: Dict[str, List[Field]] (that maps the name of the new fields to the docstring fields). Then we should use this new variable in the format function to include the new fields into the generated HTML.
We need to make a choice about the position of the new fields in the generated HTML, should they be before the regular fields or after ?
I've written a epydoc to define new field in the following way. But Unknown Field errors occur if I run pydoctor on my project. I think it's because current version of pydoctor do not support newfield for reStructuredText. Is there any other mechanism for defining new field? Or do you have any plans to update?
The text was updated successfully, but these errors were encountered: