This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Decide to use requireComponents or safe unwrap context #3440
Labels
eng:health
Improve code health
eng:ready
Ready for engineering
help wanted
Help wanted from a contributor. More complex than good first issue.
P5
Never, but will accept a patch
wontfix
Comments
NotWoods
added a commit
to NotWoods/fenix
that referenced
this issue
Aug 30, 2019
NotWoods
added a commit
to NotWoods/fenix
that referenced
this issue
Aug 30, 2019
NotWoods
added a commit
to NotWoods/fenix
that referenced
this issue
Sep 9, 2019
NotWoods
added a commit
to NotWoods/fenix
that referenced
this issue
Sep 9, 2019
NotWoods
added a commit
to NotWoods/fenix
that referenced
this issue
Sep 9, 2019
ekager
pushed a commit
that referenced
this issue
Sep 10, 2019
ekager
pushed a commit
to NotWoods/fenix
that referenced
this issue
Sep 18, 2019
boek
pushed a commit
that referenced
this issue
Sep 19, 2019
ekager
added
help wanted
Help wanted from a contributor. More complex than good first issue.
eng:ready
Ready for engineering
labels
Dec 10, 2019
there are still a few |
data-sync-user
changed the title
Decide to use requireComponents or safe unwrap context
FNX3-17019 ⁃ Decide to use requireComponents or safe unwrap context
Aug 11, 2020
kbrosnan
changed the title
FNX3-17019 ⁃ Decide to use requireComponents or safe unwrap context
Decide to use requireComponents or safe unwrap context
Aug 27, 2020
See: #17373 This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
eng:health
Improve code health
eng:ready
Ready for engineering
help wanted
Help wanted from a contributor. More complex than good first issue.
P5
Never, but will accept a patch
wontfix
Currently we use the two interchangeably throughout the code base and it doesn't seem to have reasoning behind it (or at least reasoning that is transparent to other engineers). I'm of the mind that we should just be using
requireComponents
so we don't have silent failures.┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: