Skip to content

[HOLD for payment 2023-12-29] [TS migration] Migrate 'IFrame.js' component to TypeScript #31932

Closed

Description

@melvin-bot

TypeScript migration

Make sure you read through our TypeScript's style guide, cheatsheet and PropTypes conversion table before you start working on this migration issue.

Files

Path Dependencies
src/components/IFrame.js 4

Activity

  1. pac-guerreiro commented on Nov 29, 2023

    @pac-guerreiro
    Contributor

    I am Pedro Guerreiro from Callstack - expert contributor group. I’d like to work on this job!

  2. melvin-bot commented on Dec 18, 2023

    @melvin-bot
    Author

    Triggered auto assignment to @marcaaron, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

  3. hoangzinh commented on Dec 20, 2023

    @hoangzinh
    Contributor

    hi @marcaaron , can you help to:

    1. Assign me to this issue
    2. Add the issue label "New Feature" or "Bug" to trigger adding a BZ member to this issue
      Thanks
  4. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 20, 2023
  5. 10 remaining items

  6. changed the title [-][TS migration] Migrate 'IFrame.js' component to TypeScript[/-] [+][HOLD for payment 2023-12-29] [TS migration] Migrate 'IFrame.js' component to TypeScript[/+] on Dec 22, 2023
  7. melvin-bot commented on Dec 22, 2023

    @melvin-bot
    Author

    Reviewing label has been removed, please complete the "BugZero Checklist".

  8. melvin-bot commented on Dec 22, 2023

    @melvin-bot
    Author

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.15-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2023-12-29. 🎊

    After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

    • External issue reporter
    • Contributor that fixed the issue
    • Contributor+ that helped on the issue and/or PR

    For reference, here are some details about the assignees on this issue:

  9. melvin-bot commented on Dec 22, 2023

    @melvin-bot
    Author

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@hoangzinh] The PR that introduced the bug has been identified. Link to the PR:
    • [@hoangzinh] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@hoangzinh] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@hoangzinh] Determine if we should create a regression test for this bug.
    • [@hoangzinh] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@twisterdotcom] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  10. twisterdotcom commented on Jan 2, 2024

    @twisterdotcom
    Contributor

    Payment Summary:

    Contributor: @pac-guerreiro is from an agency-contributor and not due payment.
    Contributor+: @hoangzinh is due $250 here: https://www.upwork.com/nx/wm/offer/100263336

  11. hoangzinh commented on Jan 2, 2024

    @hoangzinh
    Contributor

    Accepted. Thanks @twisterdotcom

  12. twisterdotcom commented on Jan 2, 2024

    @twisterdotcom
    Contributor

    All paid out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2TaskTypescript Migration

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions