Composites show as being under the __init__ module

Open
#162 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Locate the documentation source containing the .. automodule:: dwave.preprocessing.composites.__init__ directive and inspect how the composites are presented. Rebuild the affected API documentation and verify that the composites appear under the intended module and that the generated objects.inv supports the expected cross-references.

Written by the indexing model from the issue text.

Description

The built docs show currently like this:

Image

This is due to the placement of the .. automodule:: dwave.preprocessing.composites.__init__ directive, and it causes a problem for xrefing:

The objects.inv looks like this:

Image
Dominant language
C++
Stars
9
Forks
18
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dwavesystems/dwave-preprocessing

All issues in dwavesystems/dwave-preprocessing

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.