Open vincdargento opened 8 hours ago
Triggered auto assignment to @carlosmiceli (DeployBlockerCash
), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.
💬 A slack conversation has been started in #expensify-open-source
Triggered auto assignment to @abekkala (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
:wave: 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:
@abekkala FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
Job added to Upwork: https://www.upwork.com/jobs/~021864332553645385180
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh (External
)
Edited by proposal-police: This proposal was edited at 2024-12-04 15:50:15 UTC.
The initial value field name is "Date".
We are wrong when set description
as date here
We should convert this to description={translate('common.initialValue')} if not is date type
description={isDateFieldType ? translate('common.date') : translate('common.initialValue')}
NA
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
Edited by proposal-police: This proposal was edited at 2024-12-04 16:16:50 UTC.
Report fields - Initial value field name is "Date" for text report field
Refactor the field-rendering logic to use a switch-case structure. This approach will:
const renderFieldName = () => {
switch (reportField.type) {
case CONST.REPORT_FIELD_TYPES.DATE:
case CONST.REPORT_FIELD_TYPES.TEXT:
// return component here
return;
case CONST.REPORT_FIELD_TYPES.LIST:
// return component here
return;
default:
// return component here
return;
}
}`
### What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
N/A
As mentioned in the other proposal above, we check the type of reportField to display description
regression from https://github.com/Expensify/App/pull/50827
@carlosmiceli, I can handle this if needed, as it's a regression from my PR.
📣 @Krishna2323 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!
Offer link Upwork job Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻 Keep in mind: Code of Conduct | Contributing 📖
@carlosmiceli, I can handle this if needed, as it's a regression from my PR.
Sounds good! Thank you!
@rushatgabhane could you please review the PR above ^? This is a regression from https://github.com/Expensify/App/pull/53611
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.71-0 Reproducible in staging?: Yes Reproducible in production?: No 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: N/A Email or phone of affected tester (no customers): applausetester+khcategory18@applause.expensifail.com Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
The initial value field name is "Initial value".
Actual Result:
The initial value field name is "Date".
Workaround:
Unknown
Platforms:
Screenshots/Videos
https://github.com/user-attachments/assets/e6de8f3b-0e71-413e-8711-70266f5e9daf
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @fedirjh