fix(api): fix polling duration wrongfully marshalled #1767
Merged
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.
Description
Context
One of our customers has some problems when getting the config of the Atlar connector. After investigation, it was the custom duration struct that was failing to be marshalled before being sent to the client. A fix has been done a few weeks ago to fix the "pollingPeriod" custom duration in the configs, but Atlar has one more custom duration struct.
Solution
After investigation, it seems that the custom duration struct was not implementing correctly the Marshal interface, which was the cause of the wrong json sent through the api. Fixing this implementation allows us also to remove the api fix we've made.
Fixes PMNT-109