feat: add config parameter to disable custom stringification #288
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.
Fixes #287.
Introduced a new property
appmap.event.disableValue
to disable the custom stringification of objects during AppMap recordings. This change includes:DisableValue
property in "Properties" class to toggle stringification.Value
class to respect this property.DisabledValue
to validate functionality whenDisableValue
is enabled.Example
for testing and abats
script to verify the changes.Summary of Changes
DisableValue
in theProperties
class which can be toggled to disable the stringification of objects.false
.Value
Class to Utilize the New Property:freeze
method in theValue
class to check theDisableValue
property.DisableValue
istrue
, the object’s value is set to a placeholder ("< disabled >"
).DisabledValue
that generates an AppMap recording to verify the behavior whenDisableValue
is enabled.Example
class with atoString
method and a methoddoSomething
that returns an instance of theExample
class.bats
Test:bats
test script to compile the test files and run the new test, verifying theDisableValue
property functionality usingjq
to inspect the AppMap JSON output.