Skip to content

[$250][TS migration] Migrate 'QRCode' component to TypeScript #25000

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/QRCode/index.js 5

Activity

  1. melvin-bot commented on Sep 11, 2023

    @melvin-bot
    Author

    This issue has not been updated in over 15 days. eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  2. VickyStash commented on Oct 19, 2023

    @VickyStash
    Contributor

    Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue.

  3. 20 remaining items

  4. changed the title [-][TS migration] Migrate 'QRCode' component to TypeScript[/-] [+][$250][TS migration] Migrate 'QRCode' component to TypeScript[/+] on Nov 16, 2023
  5. melvin-bot commented on Nov 16, 2023

    @melvin-bot
    Author

    ⚠️ Could not update price automatically because there is no linked Upwork Job ID. The BZ team member will need to update the price manually in Upwork.

  6. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 16, 2023
  7. melvin-bot commented on Nov 16, 2023

    @melvin-bot
    Author

    Triggered auto assignment to @greg-schroeder (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  8. melvin-bot commented on Nov 16, 2023

    @melvin-bot
    Author

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  9. AndrewGable commented on Nov 16, 2023

    @AndrewGable
    Contributor

    @greg-schroeder - Can you please pay out $250? Thanks

  10. mananjadhav commented on Nov 16, 2023

    @mananjadhav
    Collaborator

    @AndrewGable @greg-schroeder I think I'll only need a payment summary here. I can raise my request on NewDot.

  11. mananjadhav commented on Nov 23, 2023

    @mananjadhav
    Collaborator

    @greg-schroeder @AndrewGable quick bump on the payout summary here.

  12. greg-schroeder commented on Nov 26, 2023

    @greg-schroeder
    Contributor

    Sorry, I was out most of the week for the holiday.

  13. greg-schroeder commented on Nov 26, 2023

    @greg-schroeder
    Contributor

    @mananjadhav please make a manual request in NewDot for $250 for the reviewer role

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

Metadata

Metadata

Labels

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions