-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue 308 #321
Issue 308 #321
Conversation
fix: don't attempt to transform floats that are Inf or NaNs fix: check type for strings in toml config Signed-off-by: Iain Anderson <iain@iotechsys.com>
Signed-off-by: Iain Anderson <iain@iotechsys.com>
Signed-off-by: Iain Anderson <iain@iotechsys.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iain-anderson In edgex_propertytype_tostring have replaced strcasecmp with strcmp, does this mean type names are now case sensitive ?
Yes but they should be normalized during validation in core-metadata (code here) |
@iain-anderson And this is the only path to this function ? |
@SteveOss it will only be used when receiving a device profile update notification from metadata, or when requesting a device profile from metadata (when a device is instantiated for which we don't yet have the profile definition) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
PR Checklist
Please check if your PR fulfills the following requirements:
If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/device-sdk-c/blob/master/.github/CONTRIBUTING.md
What is the current behavior?
Issue Number: #303 #308
What is the new behavior?
Checks added for CheckInterval, ProfilesDir being unset
Changed type names
Added MaxRequestSize configuration option and enforced in http processing
Does this PR introduce a breaking change?
Type names in device profiles are now case-sensitive (in practice this
is a breaking change in core-metadata where they will be validatedshould not be an issue as they are normalised in core-metadata)New Imports
Specific Instructions
Other information