1.3.2

What's Changed

Bug Fixes

• FFM-12241 Fix jsonVariation encoding issue by @erdirowlands in #44

The jsonVariation method previously returned double-escaped JSON strings, requiring developers to manually decode the strings to extract valid JSON objects. This issue has now been resolved.

Old Behavior (Double-Escaped JSON):

The method returned JSON strings that required an additional decoding step, as the content was escaped twice. For example:

"\"[{\\\"key\\\":\\\"value\\\"}]\""

This required developers to:

1. Decode the outer JSON string.
2. Decode the inner JSON string to access the actual JSON object.

New Behavior (Properly Escaped JSON):

The method now returns correctly formatted JSON strings without requiring manual unescaping:

"[{\"key\":\"value\"}]"

This allows you to decode as JSON, for example, using JSONSerialization.jsonObject

Impact on Developers:

If you previously relied on manually decoding the returned jsonVariation output to handle the double-escaping, you should stop doing this immediately. The old format was a bug, and with this fix, manual unescaping is no longer necessary.

Recommended Actions:

• Review Your Decoding Logic:
• Remove any extra unescaping or decoding steps applied to jsonVariation results.
• Test Your Application:
  • Ensure the corrected JSON format integrates with your application’s JSON parsing.

Full Changelog: 1.3.1...1.3.2