We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
还记得刚开始写前端的时候,如果我们按照顺序执行,牺牲代码质量,比如模块化,代码可重用,还有可维护,下面列举一个例子,这个例子看完之后有种似曾相似的感觉 这个问题叫做callback hell
有哪些规约可以减少上面的痛点呢
The text was updated successfully, but these errors were encountered:
未完待续,太懒了,先截图凑合吧
Sorry, something went wrong.
No branches or pull requests
异步编程的痛点
还记得刚开始写前端的时候,如果我们按照顺序执行,牺牲代码质量,比如模块化,代码可重用,还有可维护,下面列举一个例子,这个例子看完之后有种似曾相似的感觉
这个问题叫做callback hell
callback discipline
有哪些规约可以减少上面的痛点呢
命名好我们的函数会对栈追踪起到更好的效果(stack trace)
重构后的代码
The text was updated successfully, but these errors were encountered: