Skip to content

Implement provide-canBeMissing-in-useOnyx rule #142

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

Conversation

fabioh8010
Copy link
Contributor

@fabioh8010 fabioh8010 commented Mar 23, 2025

This PR implements a new ESLint rule to enforce useOnyx calls to provide the canBeMissing option. It's intended to be used on .eslintrc.changed.js, that will only run for the changes files of a PR.

This rule should only be used when the Onyx PR is merged and its release available in E/App.

Issue: Expensify/App#58499

Screenshot 2025-03-23 at 14 56 01

@fabioh8010 fabioh8010 marked this pull request as ready for review March 23, 2025 15:32
iwiznia
iwiznia previously approved these changes Mar 24, 2025
@iwiznia
Copy link
Contributor

iwiznia commented Mar 24, 2025

I think you forgot to add a HOLD to this, right? Adding it just in case

@iwiznia iwiznia changed the title Implement provide-canBeMissing-in-useOnyx rule [HOLD] Implement provide-canBeMissing-in-useOnyx rule Mar 24, 2025
@fabioh8010
Copy link
Contributor Author

@iwiznia We can merge now if you want too, I will enable it in a E/App PR later when the Onyx changes are merged and released.

@iwiznia
Copy link
Contributor

iwiznia commented Mar 24, 2025

Ah ok good to know

@iwiznia iwiznia changed the title [HOLD] Implement provide-canBeMissing-in-useOnyx rule Implement provide-canBeMissing-in-useOnyx rule Mar 24, 2025
@iwiznia iwiznia merged commit f988267 into Expensify:main Mar 24, 2025
3 checks passed
@os-botify
Copy link
Contributor

os-botify bot commented Mar 24, 2025

🚀 Published to npm in 2.0.78 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants