-
Notifications
You must be signed in to change notification settings - Fork 0
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
Create unit improved #14
base: development
Are you sure you want to change the base?
Conversation
…nto CreateUnitImproved
defaultMeterMinimumValue:Number.MIN_SAFE_INTEGER, | ||
defaultMeterMaximumValue:Number.MAX_SAFE_INTEGER, |
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.
Please use
import { MAX_VAL, MIN_VAL } from '../../redux/selectors/adminSelectors';
Both refer to the same value but the above import is used in places where ever the requirement is for max and min values. So please use the above import to mantain uniformity in the code
<Row xs='1' lg='2'> | ||
{/* default Meter Minimum Value input */} | ||
<Col><FormGroup> | ||
<Label for='defaultMeterMinimumValue'>{translate('default.meter.minimum.value')}</Label> |
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.
Coordinate with @lawsj on the translations
defaultMeterMinimumValue: 0, | ||
defaultMeterMaximumValue: 0, |
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.
For no unit, the values should be -Infinity,Infinity. Please refer to the meeting recording for any clarification
default_meter_minimum_value INTEGER NOT NULL, | ||
default_meter_maximum_value INTEGER NOT NULL, |
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.
As discussed the new columns must be added via ALTER
Description
I gone further into implementing the CreateUnit Functionality. Ive added more connection to the backend aswell has fix some impletation issues
Fixes #[issue]
(In general, OED likes to have at least one issue associated with each pull request. Replace [issue] with the OED GitHub issue number. In the preview you will see an issue description if you hover over that number. You can create one yourself before doing this pull request. This is where details are normally given on what is being addressed. Note you should not use the word "Fixes" if it does not completely address the issue since the issue would automatically be closed on merging the pull request. In that case use "Partly Addresses #[issue].)
Type of change
(Check the ones that apply by placing an "x" instead of the space in the [ ] so it becomes [x])
Checklist
(Note what you have done by placing an "x" instead of the space in the [ ] so it becomes [x]. It is hoped you do all of them.)
Limitations
currently giving errors due when creating units