Skip to content
This repository has been archived by the owner on Jun 24, 2021. It is now read-only.

no-alert? #70

Open
bobheadxi opened this issue Aug 25, 2018 · 3 comments
Open

no-alert? #70

bobheadxi opened this issue Aug 25, 2018 · 3 comments

Comments

@bobheadxi
Copy link
Contributor

JavaScript’s alert, confirm, and prompt functions are widely considered to be obtrusive as UI elements and should be replaced by a more appropriate custom UI implementation... This rule is aimed at catching debugging code that should be removed and popup UI elements that should be replaced with less obtrusive, custom UIs.

https://eslint.org/docs/rules/no-alert

Relevant code: https://github.com/nwhacks/nwhacks2019/blob/7436578f3a2f1177463cbd0ef80323a15df597f1/web/components/application/hacker/Hacker.js#L53

Thoughts, @mingyokim ?

@mingyokim
Copy link
Contributor

I’d say alerts are fine as long as design team is fine with it, since we don’t have the custom UI for alerts ready to use right now. Alerts would help us move forward faster to have an MVP without compromising functionality

@bobheadxi
Copy link
Contributor Author

Yeah, I'm fine with it for now, just noticed our linter complaining.

Any thoughts on this @sherryyx / design team? (speaking of which would be nice if we could just tag @nwhacks/design 😛 )

Marking as low-priority for now

@sherryyx
Copy link

@bobheadxi Yeah let’s just leave it for
now!

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

No branches or pull requests

3 participants