We need to suppress the default argument in the signature when we're
doing matching as you can't...

Attempt to make it a little more approachable for new people. It had
become quite a mix of links...

We pass the 'outline' option through to the filter so that we don't get
the function description...

Thanks for fixing the css class output and improving the keyword
handling for declarations.

The value of 'const' can be 'no' so checking for its truthiness is not
suitable, instead we can ...

This sets the CSS class of the emitted HTML element to the object kind
(e.g., `class` or `struct...

And document the set up.

This involves switching the EndsWithFilter to handle a list of options...

We've had a bug report that if we have a c-style function in a header
file & implementation file...

Slightly better form I think.

We want to hide the declname and defname attributes from the param
nodes for the signature rende...

We change the warning mechanism so that we can provide the raw_text and
the nodes if desirable.
...

The previous approach tried to read appropriate data out of the xml
object hierarchy and use it ...

And extend the class example to have an impl file as well for
testing.

Tired of stuff lying around confusing the status but still want some of
that stuff for development.

Also if there are several candidates, if all candidates' arguments are
identical.

When a function is both declared and implemented, doxygenfunction fails with the message:

Warni...

So that innerclasses respond properly the :members: option having
specific members listed.

Othe...

As they should be basically the same thing. This introduces public,
private, protected & undoc c...

And fix up the warning message.

And fix doxygengroup/namespace typo.

The implementation is just style.

The docs cover an example of outline working as expected.

Although already been documented, the outline flag has not been
implemented to the doyygengroup ...

- a forgotten variable definition
- duplicate flag entry

Thanks for writing the doxygennamespace directive.

By copying over the group docs and changing them appropriately.

They are so close in purpose and implementation that we combine them
into common methods and bas...

As the 'file' part is an unnecessary extra which breaks the trend with
other example projects.

It seems I completely failed to proofread the copy and paste of examples
from the class docs to ...

It was written prior to the RenderContext introduction and rebased.

Improved to remove the empty note and add the required target for the
namespace link from the di...

This commit adds a directive to include namespaces very similar to the
already existing `doxygen...

As all the actually description text is put into <para> elements, the
text between these element...

They can be simplified a little. I think.

An attempt to explain some of what is going on.

This is more reliable but also only matches the memberdefs and not the
sectiondefs so we're losi...

Top level public objects like c-functions are now filtered based on
their memberdef 'prot' attri...

We are going to need more information about where we are in the
hierarchy when rendering. Specif...

As it was to account for the different sectiondef 'kind' values but now
as we're looking at the ...

It turns out that if you define custom groups then the sectiondefs
have type of 'user-defined' i...

For group and make some tweaks to formatting in general.

We add a new filter builder method to constuct a filter for innerclasses
(public, protected and ...

We refactor the create_private_members_filter method so that it can do
either private or protect...

It was a pretty random order before. This makes sense. We group the
auto-directives with the pairs.

We just let it pass down to the creation of the members filter for the
classes and do its stuff.

To clarify their construction a little and leave more room for
documentation.

I failed to update it when changing away from :sections:.

We split the filtering of top level C-language kinds of sectiondefs out
to a separate filter so ...

We rewrite it to deal in terms of our new members options rather than
the sections concept. This...

It is a little more complex than repeating the members and
private-members options as the undoc-...

Rather than using 'type' because it is a few less characters and risk
confusion with an actual '...

The filters were getting a little complex & ugly to declare as nested
object declarations so we ...

Which may or may not be more readable. Actual if-statements would be
more readable, but we can o...

This was in here before we started rewriting it. I'm not sure of an
example which exercises this...

It doesn't seem to fit with the use case. If it is an option, what does
it mean? Public members ...

I forgot the __or__ method and apparently __contains__ has to return a
True or False so we switc...

We account for the :sections: option when extracting the content from
the doxygen group when ren...

Previously it was hard coded to [public*, func*] but now we default to
that but make it configur...

So that we're not left in a detached HEAD state as we were previously. I
keep forgetting and the...

It seems that top level functions go into their own sectiondef with a
'func' 'kind'. We'd really...

We add public and private functions to our group.h code and then extend
the documentation to cov...

To take advantage of the OrFilters which can now take multiple arguments
so we don't have to cre...

As we think we're going to need it for the groups shortly.

We missed those on the previous effort. Here we move the warning code in
directive/base.py and d...

Having separated out the section filter code to a separate method we can
easily call it to creat...

We use git to detect the latest tag and report the tag version if we're
sitting on that tag and ...