microsoft / microsoft/win32metadata
WIN32_FIND_DATAA issue with CfGetPlaceholderStateFromFindData and FindFirstFile
Open
Nobody has claimed this yet.
bug
- Dominant language
- C++
- Stars
- 1.5k
- Forks
- 149
- Avg merge
- 5d 16h
- Merged PRs (30d)
- 4
Description
Actual behavior
CfGetPlaceholderStateFromFindData takes an ANSI WIN32_FIND_DATAA but it may be unicode only
Expected behavior
CfGetPlaceholderStateFromFindData should accept WIN32_FIND_DATAW
Repro steps
NativeMethods.txtcontent:
CfGetPlaceholderStateFromFindData
NativeMethods.jsoncontent (if present):
- Any of your own code that should be shared?
Context
- CsWin32 version: [e.g.
0.4.422-beta] - Win32Metadata version (if explicitly set by project):
- Target Framework: [e.g.
netstandard2.0] LangVersion(if explicitly set by project): [e.g.9]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the NativeMethods.txt entry for CfGetPlaceholderStateFromFindData and trace how the Win32 metadata represents that API and its FindFirstFile data parameter. Check the generated metadata or relevant validation tests, if present, and confirm that the API accepts the expected wide-character structure without breaking existing generation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100