Skip to content
This repository has been archived by the owner on May 7, 2020. It is now read-only.

Improve usage of normalizer for configuration properties in Automation module. #1938

Merged
merged 1 commit into from
Aug 2, 2016

Conversation

danchom
Copy link
Contributor

@danchom danchom commented Jul 29, 2016

Signed-off-by: Yordan Mihaylov j.mihailov@prosyst.com

Up to this PR only configuration properties which has number object value were normalized to BigDecimal values. Unfortunately the boolean and string objects were not changed.
Now the automation module uses NormalizerFactory to achieve Normalizer base on its config descripion parameter meta data.

Signed-off-by: Yordan Mihaylov <j.mihailov@prosyst.com>
@danchom
Copy link
Contributor Author

danchom commented Jul 29, 2016

I've changed a little bit ConfigUtil and NormalizerFactory to remove dependency to the guava lib third party lib,

@kaikreuzer kaikreuzer merged commit f980c9d into eclipse-archived:master Aug 2, 2016
@kaikreuzer
Copy link
Contributor

thanks!

cdjackson added a commit to cdjackson/smarthome that referenced this pull request Aug 2, 2016
* master:
  Initial commit of persistence extensions (eclipse-archived#1872)
  fixed concurrency issues (eclipse-archived#1950)
  Fix usage of normalizer in Automation module. (eclipse-archived#1938)
  changed log level for config validation (eclipse-archived#1953)
  Enhancement to hue binding documentation (eclipse-archived#1952)
  Change the hue binding to include the thing type id in the thingUID again (eclipse-archived#1946)
@danchom danchom deleted the normalize branch December 8, 2016 12:04
@kaikreuzer kaikreuzer added this to the 0.9.0 milestone Nov 30, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants