Skip to content

Field mapping breaks when handling UTF-16 data #36

Description

@zackkatz

To reproduce:

  1. Load a UTF-16 CSV
  2. Create a \DataKit\DataViews\Field\StatusIndicatorField
  3. Use ->mapping() to try and map a status

What you see:
There aren't any matches other than inactive because the match fails due to different bytes being compared.

Then use a UTF-8 CSV and it works.

See https://gravitykit.slack.com/archives/C076T3EQNS1/p1725134616822689 for a video (with sensitive data).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions