feat: add change_message attribute to field content #9
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.
Title
Upgrade typedstruct dependency and add JSON encoding for FieldContent struct
Type of Change
Description
This pull request includes the following updates:
typed_struct
to the maintainedtypedstruct
package to ensure future support and compatibility.FieldContent
struct in theExPass.Structs.FieldContent
module. The new encoder convertsFieldContent
struct data into camelCase keys and filters outnil
values. This is critical for ensuring consistent interaction with external systems via APIs.change_message
in theFieldContent
struct, which allows descriptive messages when field values change.Testing
FieldContent
to include validation of thechange_message
field.nil
values.Impact
typedstruct
may introduce minor changes in struct behavior, but no breaking changes are expected.FieldContent
JSON data should now receive properly formatted camelCase keys, ensuring compatibility with standardized systems.change_message
follows the format requirements (%@
placeholder).Additional Information
N/A