Update CSV cmdlet -Delimiter parameter description
#12617
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
This PR clarifies the deserialization behavior when the specified delimiter doesn't match the actual delimiter in the input data. Before this change, the verbiage for
Import/ConvertFrom-Csv -Delimiterwas ambiguous, potentially suggesting output wouldn't be a custom object if the wrong delimiter is used.In addition, this adds a note regarding special character double-quoting to all docs. Previously, the note was only present in the
Import-Csvdocs, but it's applicable to/useful for all CSV cmdlet-Delimiterdescriptions.There are also minor style/formatting changes.
PR Context
This also applies to:
-Delimiterisn't specified and,isn't used in the input.-UseCultureis specified and the delimiter used in the input doesn't match the current culture's.PR Checklist