Per diem - The Quantity field allows float number

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.0.81-1
Reproducible in staging?: Y
Reproducible in production?: Unable to check
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #54252
Issue reported by: Applause - Internal Team
Component: Money Requests

Action Performed:

Precondition
Workspace has Per diem enabled and Per diem rates loaded

1. Go to staging.new.expensify.com
2. Go to FAB > Create expense > Per diem tab
3. Select any country
4. Select start and end dates
5. Select any Subrate
6. Enter a float number in the Quantity field
7. Click on Save

Expected Result:

The field should not allow entering a float number (similar to OldDot behavior)

Actual Result:

The Quantity field allows entering a float number and the number is trim to a integer in the Confirm details pag

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6708284_1736265757230.Per_diem-float_number.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @puneetlath (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[puneetlath]

Closing. Being handled in follow up by @shubham1206agra. Doesn't need to block.