Skip to content

Conversation

@carlossanlop
Copy link
Contributor

Follow-up of #78465

We don't want to trim the keys or the values retrieved from the extended attributes section. We want to preserved them untouched.

@jozkee
Copy link
Member

jozkee commented Nov 22, 2022

Should we mark this as a breaking change?

@stephentoub stephentoub merged commit ed1ed67 into dotnet:main Nov 22, 2022
@carlossanlop carlossanlop deleted the RemoveTrimPaxEa branch November 23, 2022 01:46
@carlossanlop
Copy link
Contributor Author

Should we mark this as a breaking change?

My gut says no. We're correcting a behavior considered a bug, not changing the way an API is working.

carlossanlop added a commit that referenced this pull request Nov 29, 2022
…attributes (#78785)

* Remove invalidation of whitespace in TryGetNextExtendedAttribute (#78465)

* Remove invalidation of whitespace in TryGetNextExtendedAttribute

* Add requested test

* Remove TrimStart in PAX extended attributes (#78707)

* Remove TrimStart in PAX extended attributes

* Adjust existing tests with two extra inline datas.

Co-authored-by: carlossanlop <[email protected]>

* Tar: Extra tests to confirm extra long paths are not treated as duplicate entries when the full path is in the extended attributes. (#78744)

Co-authored-by: carlossanlop <[email protected]>

Co-authored-by: Stephen Toub <[email protected]>
Co-authored-by: carlossanlop <[email protected]>
@ghost ghost locked as resolved and limited conversation to collaborators Dec 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants