har generated from chrome produces: "[WARN] Post data conflict (1): Both params and text are provided but the values do not match."

[tmc]

No description provided.

[legander]

Typically Chrome generated HAR includes both params and text fields in postData with the same set of data. The compiler will prefer params over text in those cases and log a warning message if both datafields are not equal.
The check that determines if the payloads are equal could perhaps be a little smarter.

[w1kman]

Correction #65 does not resolve this issue.

[tom-miseur]

For me, this warning appeared until I implemented #69, at which point params and text would match as expected (params was not decoded as part of parsing, and would therefore appear twice-encoded when passed through seralizeURLSearchParams, leading to an inconsistency). There may however be other situations where the two differ.