-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Bug]: including files with **\*.SomeExtension
may not be expanded in some cases
#9351
Comments
To add to this issue, here's the location where we include this item group. It's located inside an |
Very likely to be #406. @nickrandolph are there any files under the project directory with paths longer than |
That's interesting, so properly excluding default bin/obj folders may be of help, thanks for the insights! |
@jeromelaban please tell us if the suggestion from @rainersigwald does not work for you. |
@AR-May we've not been able to validate that it's still happening, but we'll be able to soon, we'll let you know! Thanks for the follow-up. |
This issue is marked as stale because feedback has been requested for 30 days with no response. Please respond within 14 days or this issue will be closed due to inactivity. |
@AR-May so far it's not been havening anymore, so we can close this issue. We'll comment further if it ever happens again, thanks! |
@rainersigwald We're still seeing it. We are also excluding bin/obj: |
Team triage: this issue is currently blocked by #9609. We need to improve logging to be able to investigate. |
Issue Description
See unoplatform/uno.templates#354
In csproj, we simply have
<PRIResource Include="**\*.resw" />
Then, we run a target that adds these to AdditionalFiles as follows:
https://github.com/unoplatform/uno/blob/1c635068111de02977090c8379206a4caac40b3d/src/SourceGenerators/Uno.UI.SourceGenerators/Content/Uno.UI.SourceGenerators.props#L359
We end up with:
Steps to Reproduce
Not consistent, but detailed above.
Expected Behavior
**\*.resw
should be expanded properly.Actual Behavior
Error
Analysis
No response
Versions & Configurations
No response
The text was updated successfully, but these errors were encountered: