efl-mono: Use alternate docs when a property has no doc

Summary:
Use the getter or the setter documentation when a property has no documentation.
This is not ideal (all properties should have documentation!) but at least we
have less undocumented properties.
See for example Efl.Canvas.Vg.Above.

Test Plan:
The Efl.Canvas.Vg.Above property in src/lib/evas/canvas/efl_canvas_vg_node.eo.cs
was previously undocumented because that property (inherited from Efl.Gfx.Stack)
has no docs, only its getter has docs.

Reviewers: lauromoura

Reviewed By: lauromoura

Subscribers: cedric, #reviewers, #committers

Tags: #efl

Differential Revision: https://phab.enlightenment.org/D7500
This commit is contained in:
Xavi Artigas 2018-12-21 15:21:46 +01:00
parent c84580cc05
commit 3b9f8f8d6a
1 changed files with 9 additions and 1 deletions

View File

@ -843,7 +843,15 @@ struct property_def
Eolian_Function_Type type = ::eolian_function_type_get(function);
if (type == EOLIAN_PROP_GET || type == EOLIAN_PROP_SET || type == EOLIAN_PROPERTY)
documentation = eolian_implement_documentation_get(implement, EOLIAN_PROPERTY);
{
documentation = eolian_implement_documentation_get(implement, EOLIAN_PROPERTY);
// If property-level documentation is empty, use the getter- or setter-level
// docs as fallback (if present).
if (documentation.summary.empty())
documentation = eolian_implement_documentation_get(implement, EOLIAN_PROP_GET);
if (documentation.summary.empty())
documentation = eolian_implement_documentation_get(implement, EOLIAN_PROP_SET);
}
}
};