Skip to content

Conversation

@fpelliccioni
Copy link
Contributor

Fixes #469

It took me quite a while to investigate where the SVG "house" icon is being generated.

image

I explored various parts of the codebase and toolchain but couldn't locate it. As of now, I still don’t know if this behavior can be modified. Based on my research so far, it doesn't seem to be controlled by MrDocs but rather by subsequent tools in the toolchain, such as Antora.

I came up with this change—not ideal, but it’s a starting point to evaluate if it’s acceptable. If it’s not, any pointers on how to control the house icon generation would be much appreciated. As I mentioned, it doesn’t seem to be within the MrDocs repository.

@cppalliance-bot
Copy link

An automated preview of the documentation is available at https://771.mrdocs.prtest2.cppalliance.org/index.html

See: https://mrdocs.com/docs/mrdocs/develop/generators.html#dom_reference
--}}
{{~#if (and parent parent.name)~}}
xref:{{{remove_prefix parent.url "/"}}}[⬆]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

xref is not valid HTML. These common partials are used by both generators. See the other partials in this folder.

Breadcrumbs are included in the symbol template as an alternative.
}}
= {{> symbol/qualified-name symbol }}
= {{> symbol/enclosing-namespace symbol }}{{> symbol/qualified-name symbol }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This worsens things because we have removed the links to other enclosing namespaces, which the qualified-name partial does. It's removing a feature rather than including one.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was surprised the test files didn't change. I think it's because tests bypass the wrapper. But losing this information about the enclosing namespaces in real documentation like Boost.URL sure looks bad.

@alandefreitas
Copy link
Collaborator

See #469 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Need a button to navigate to the enclosing namespace

3 participants