-
-
Notifications
You must be signed in to change notification settings - Fork 806
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
include_file
should overrule include_ext
#350
Comments
Is
|
Yes it's working for me, but the extension needs to be in
|
Essentially, a file can now be in `include_file` without having its extension in `include_ext`, which I generally think is the expected behaviour because explicit filenames are more specific than extensions. Fixes: air-verse#350
#358 should fix this. |
Essentially, a file can now be in `include_file` without having its extension in `include_ext`, which I generally think is the expected behaviour because explicit filenames are more specific than extensions. Fixes: air-verse#350
Essentially, a file can now be in `include_file` without having its extension in `include_ext`, which I generally think is the expected behaviour because explicit filenames are more specific than extensions. Fixes: air-verse#350
i personally viewed the two as mutually exclusive. i would want to be able to include a single file and not have to add it to the i'm guessing that's what #358 is attempting to address? |
Exactly, after #358, |
Looks like #416 is the latest PR for this. Would love to get this in. I want |
(#416) * feat: Make include_file overrule include_ext * feat: Make include_file overrule include_ext unittest
…ase_on: air-verse#358 (air-verse#416) * feat: Make include_file overrule include_ext * feat: Make include_file overrule include_ext unittest
On
master
branch:This config will not trigger a reload when
openapi.yaml
changes because its extension is missing ininclude_ext
. I would say that the check viainclude_ext
should be skipped in case of explicit inclusion viainclude_file
.The text was updated successfully, but these errors were encountered: