-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
package-folder-prefix quietly excludes libraries without a canonical prefix #82
Comments
I think we could figure out which top-level folders are package folders by:
I looked through the bundle, and there are few library packages that are missing @kattni @sommersoft (and anyone else) does this make sense to you? |
These appear to be packages without
|
@dhalbert I think that's fine to add |
I'm not entirely clear on how the Adabot check for libraries and examples and so on being named properly works though. Would this break that? |
I think those examples are packages that also need |
The https://github.com/adafruit/Adafruit_CircuitPython_asyncio library is a package of multiple library files, but its package folder does not start with
adafruit_
: it is simplyasyncio
. Because the package folders are filtered to match the--package-folder-prefix
argument, which defaults toadafruit_
,asyncio
is not included in the adafruit bundle, though it should be.I could special-case it, and maybe that's the short-term solution. But what is the reason for the existence of
--package_folder_prefix
(which can be a list of multiple prefixes, separated by,
). Is it just to identify the package folder easily? Would it be better just to skip the directories that we know are not package folders, such asdocs
andexamples
? There should then be only one leftover directory, which is the package folder, if there is a package.#61 is related, as is this comment by @tannewt that we should use an ignore list instead of an accept list.
The text was updated successfully, but these errors were encountered: