Conversation
|
Sorry for meddling in, it seemed a relatively monotone and tedious, but also easy task for me (i.e. "good first issue"/"good for newcomers" 😄). I disabled marking empty functions and interfaces as an error? What about static classes, and non-null assertions? Do we allow those, or not? |
…g, async where is a promise required, relay subbmitAnswer() gets a number, now it's ensured + empty function and inerface warnings shouldn't be serious errors, right?
OregSamSas
force-pushed
the
feature/181-fix-eslint
branch
from
9109c54 to
5e2d6be
Compare
|
I rebased the branch and solved merging conflicts. (In the |
… is not reassigned in scope, remopve unneccessary es-lint ignorations, type issues, imports), and type error with relay input
…uldn't have a transparent background I think
…logs shouldn't have a transparent background I think" (Since unrelated, movedd to a new branch and to different PR.) This reverts commit 2c3e1d8.
…idea why needed ever: the && operator short-circuits before evaluating right operation (<TeamDetailDialog>) if variable on left is null
|
Don't we need the |
|
Also, what is |
…d in these files, I think checking whether objects are non-null would complicate code more then just asserting they aren't)
…handling them being null would overcomplicate code there)
|
2 participants
Issue: #181