Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mention "modern" fake timers implementation in docs #10022

Closed
wants to merge 2 commits into from

Conversation

PavelPolyakov
Copy link

Summary

Docs update. It's currently difficult to find out, that it's even possible to try this new implementation. I've accidentally met it in the release notes.

Test plan

none

It's currently difficult to find out, that it's even possible to try this new implementation. I've accidentally met it in the release notes.
@facebook-github-bot
Copy link
Contributor

Hi @PavelPolyakov!

Thank you for your pull request and welcome to our community.We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file.

In order for us to review and merge your code, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

@thymikee thymikee requested a review from SimenB May 11, 2020 14:11
@jeysal
Copy link
Contributor

jeysal commented May 11, 2020

Thanks! @SimenB does this go far enough or would you want this guide to explicitly recommend using 'modern'?

@SimenB
Copy link
Member

SimenB commented May 11, 2020

I think we should recommend it. It'll be the default in the next major, and the sooner people migrate the better 😀

docs/TimerMocks.md Outdated Show resolved Hide resolved
@jeysal
Copy link
Contributor

jeysal commented May 11, 2020

I wonder though: What will happen after the default changes? Lots of people with unnecessary 'modern' in their codebase :|
If the change is non-breaking for the majority of people (no idea if it is) maybe it's fine to not give the recommendation to everyone now?

Co-authored-by: Simen Bekkhus <sbekkhus91@gmail.com>
@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

2 similar comments
@facebook-github-bot

This comment has been minimized.

@facebook-github-bot

This comment has been minimized.

@SimenB
Copy link
Member

SimenB commented May 11, 2020

Lots of people with unnecessary 'modern' in their codebase :|

Not sure I think this is an issue. It's a search&replace away. Can probably add a lint rule or codemod that can fix it (we probably want one so FB can go the other way - add 'legacy' to all without arguments)

If the change is non-breaking for the majority of people (no idea if it is)

It should be

@codecov-io
Copy link

Codecov Report

Merging #10022 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master   #10022   +/-   ##
=======================================
  Coverage   64.00%   64.00%           
=======================================
  Files         297      297           
  Lines       12528    12528           
  Branches     3093     3093           
=======================================
  Hits         8018     8018           
  Misses       3860     3860           
  Partials      650      650           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0e0eeed...fc640bd. Read the comment docs.

@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@SimenB
Copy link
Member

SimenB commented Feb 23, 2022

Landed in #12317

@SimenB SimenB closed this Feb 23, 2022
@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants