You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Quite a few distributions have only one extension and no documentation file other than the README. Authors can get around this by adding the README under the docfile key in the provides section, but it seems silly.
So, add a rule to the indexer such that, if the distribution:
Has only one extension
Has no documentation file for that extension
Has a README
Then automatically index the README as documentation.
The text was updated successfully, but these errors were encountered:
It looks as though if authors set the docfile key to the README it doesn't show up at all. Example: mongo_fdw 1.0.0. So authors can't work around it. :-(
The indexer wasn't really paying attention to the `docfile` field in
`provides` objects, other than to be sure its value was a file to try
to index. Instead is just looked for doc files where the file name was
the same as the extension name. This works okay for distributions that
follow that rule strictly. But many distributions point to the
`README` as the doc file (as mentioned in #12), and others point to
completely different file (as in #10).
So capture much earlier that an extension has pointed to a specific
doc file, and track that relationship throughout the indexing process.
Add test cases to be sure it works.
Resolves#10.
Quite a few distributions have only one extension and no documentation file other than the
README
. Authors can get around this by adding theREADME
under thedocfile
key in theprovides
section, but it seems silly.So, add a rule to the indexer such that, if the distribution:
README
Then automatically index the
README
as documentation.The text was updated successfully, but these errors were encountered: