-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add support for invalid char in file #24759
Conversation
API change check API changes are not detected in this pull request. |
@EmmaZhu I'd thought that we fixed the issue in codegen and core to support |
118dc1d
to
9aec67a
Compare
@jeremymeng , the content and attribute is passed from XML correctly. This PR is to decode the directory name or file name from the passed content. This way the input file name would be the same with the one gotten from listing. |
9aec67a
to
d030630
Compare
d030630
to
df4c1a8
Compare
@EmmaZhu got it. thanks for the explanation! |
Add support for file invalid char
- port tests - use isBrowser from core-util
- port tests - use isBrowser from core-util - port the source changes - re-generate client - update test resource names to use different variable names. New recorder unique names are slightly different from previous version and cause same name to be retrieved for "dir" variable. - add recordings
Add support for file invalid char