This was added by !60, so wasn't included in !59.

Signed-off-by: Simon McVittie <smcv@debian.org>

build: Add meson_options.txt to setuptools sdist

See merge request GNOME/gi-docgen!61

When walking the ancestor tree we might end up resolving an unqualified
type name. This usually implies that the type comes from the same
namespace.

If the namespace has a type with the same name of the parent, for
instance:

  Foo.Device inherits from Bar.Device

and we get "Device" from the Foo namespace, instead of "Foo.Device",
then we're going to look for "Device" in the "Bar" namespace, thus
ending up in a loop.

gir: Deal with unqualified ancestor names

See merge request GNOME/gi-docgen!62

Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>

main.js: bind 's' key to focus on search input

See merge request GNOME/gi-docgen!63

We know that the namespace object is not None.

Fix issues found by Coverity

Closes #78

See merge request GNOME/gi-docgen!65

Missing comma in the middle of an array.

Fixes: #79

The dot can be confused with actual syntax, so we should use something
else to separate the clickable elements of the heading.

Instead of hard coding the separator, we can use an empty <span> and
then use CSS to fill it out.

Fixes: #81

template: Use a stylable separator for the heading

Closes #81

See merge request GNOME/gi-docgen!66

There are far, far too many false positives.

Fixes: #80

Remove gtk-doc function matching

Closes #80

See merge request GNOME/gi-docgen!67

We were parsing them out of the gir file, but not
handing them into the templates.

Make (optional) annotations work

See merge request GNOME/gi-docgen!68

Tweak the text for the generated rows.

The introspection data turns GError** arguments into a `throws`
attribute. We already add the argument when generating the declaration
of a method or function, so we also need to generate the corresponding
argument description.

Fixes: #86

Capitalise the first character of the first line, and add a period at
the end if one isn't found.

Reword the generated content:

 - expand the "direction" using a proper explanation instead of in, out,
   or in-out
 - refer to argument or return value
 - structure the return value table like the arguments one
 - add style classes to the tables
 - check for array or list independently from the generated link

We also make sure that every callable template follows the same pattern
for the arguments and return value section.

Use the muted text color for the generated content, while keeping the
full text color for the description and name.

Methods refer to an instance, so we can have a different blurb for the
ownership transfer note.

Rework the arguments and return value tables for callables

Closes #84 and #86

See merge request GNOME/gi-docgen!69

If 'dot' is not available there's no point in checking the
show_class_hierarchy configuration key: we know it won't work.

Fixes: #88

config: Handle missing dot

Closes #88

See merge request GNOME/gi-docgen!70

We can determine a type ourselves, just like we can determine symbols.

Of course, using a generic `type` fragment will require a type
resolution pass from any other tool parsing the documentation embedded
into the GIR data.

The type names are either fully qualified, or relative to the current
*namespace*.

Specify a minimum width for the cell with the argument name.

Fixes: #88

Constructors, type functions, and signals are all callables and they
should have the same layout as methods, functions, and virtual
functions.

template: Add missing callables from the arguments refactor

See merge request GNOME/gi-docgen!73

template: Give more room to argument names

Closes #88

See merge request GNOME/gi-docgen!72

Support generic type fragment for linking types

See merge request GNOME/gi-docgen!71

We want to hide it into the ast.Repository class, so we can access the
various bits and blobs from the GIR. This commit has no functional
change.

Use the ancestors list of each class to build up the types hierarchy, to
avoid stopping midway through the hierarchy of a type that inherits from
a type in a different namespace.

This allows us to drop the intermediate `GInitiallyUnowned` hierarchy,
as now `GObject.InitiallyUnowned` is a recognised type.

Fixes: #48

Improve the type hierarchy generation

Closes #48

See merge request GNOME/gi-docgen!74

If the fragment is not recognised, we should warn about it.

Fixes: #89

A callback can have a type, so we should map the same protocol as
ast.Type.

Just like other types.

And handle callback types as part of the "type" fragment.

Emit warning for invalid link fragments

Closes #89

See merge request GNOME/gi-docgen!75

We use the `callback` fragment to link to callback types.

The `type` fragment can be used with any type.

If the documentation block ends with something that is not a letter then
it's likely we're going to break something, like a code block marker.