#779 - Added integer checks to numerical fields Timeline and Budget I…

[glacierA]

…mpact

Changes

Added checks for integer values when creating change requests to prevent decimal inputs in Timeline/Budget Impact fields.

Notes

Any other notes go here

Test Cases

None (tests for create change request page seem scarce?)

Screenshots (if applicable)

To Do

None? Does it make sense for things to only be integers? Should we allow people to add 1.5 weeks or a couple of cents to the budget?

Checklist

It can be helpful to check the Checks and Files changed tabs. Please review the contributor guide and reach out to your squad if anything is unclear. Please request reviewers and ping on slack only after you've gone through this whole checklist.

• [x] All commits are tagged with the ticket number
• [x] No linting errors
• [x] No newline at end of file warnings
• [x] All code follows repository-configured prettier formatting
• [x] No merge conflicts
• [x] All checks passing
• [x] Screenshots of UI changes (if applicable)
• [x] Remove any not-applicable sections
• [x] Assign the PR to yourself
• [x] PR is linked to the ticket
• [x] No package-lock.json changes (unless dependencies have changed)
• [x] Request reviewers & ping on Slack

Closes Northeastern-Electric-Racing/FinishLine#81

[Ari-S-123]

Do you think you could ban non-numeric input for good measure?