Skip to content
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

Custom rate and named standard rate for units (Issue #1216) #1387

Closed
wants to merge 30 commits into from

Conversation

gyordong
Copy link
Contributor

Description

This PR adds a custom rate box for unit creation and edit.

Fixes #1216

Type of change

  • Note merging this changes the database configuration.
  • This change requires a documentation update

Checklist

  • [X ] I have followed the OED pull request ideas
  • [X ] I have removed text in ( ) from the issue request
  • [X ] You acknowledge that every person contributing to this work has signed the OED Contributing License Agreement and each author is listed in the Description section.

Limitations

gyordong and others added 30 commits July 11, 2024 11:00
…t value to custom input if nonstandard value
- Update unit edit logic for useEffect more
- Change custom sec in rate to require enter
- Disable save if not changed and incomplete custom input
- use setState and not directy set state
- consistently use === & !==
- Added SHL comments for original developers to look at and then remove
- Formatting
- Minor edit

Note create unit does not have new logic and bar may need
to be update to be similar
Note that @gyordong worked with me on these changes.

- Also has comments with ?? on items to do.
- Not carefully tested/completed.
…ts on customratevalid(), included customratevalid in editunit's canSave useEffect check to fix a bug with negative numbers.
@huss huss changed the title Issue #1216 Custom rate and named standard rate for units (Issue #1216) Nov 16, 2024
@huss
Copy link
Member

huss commented Nov 16, 2024

@gyordong I started to review this PR and found changes that don't seem related to the work done. I looked into this and found that previously merged changes seem to be gone in several files. One example is processData.js (line 787-8). Did you have merge conflicts when you brought in development? I see a commit with the msg "fixing mrge" on 11/15/24 but did not easily determine that is where the change happened. The bottom line is I'm nervous about these changes and what may now be out of sync with development. I think this needs to be resolved carefully (and let me know if you think I am wrong about this). If we should discuss more then please let me know.

@gyordong gyordong closed this Nov 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

standard choices for sec. in rate
3 participants