Skip to content
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

Tag possible error prone code points #1564

Merged
merged 1 commit into from
Dec 21, 2018

Conversation

Martii
Copy link
Member

@Martii Martii commented Dec 21, 2018

  • These are mostly comments in this PR
  • Normalized a few more identifiers to their standards for easier grep'ing. I'm sure there's more.
  • Some of these may be silent as intended... they should be denoted as such... like fallthrough for switch should be normally
  • Some of these assume that AWS S3 and MongoLabs are perfectly connected and no issues... bad idea. This is what I was describing. We need [Graceful failure #37](Graceful failure) whether it's a comment, a console message, a page, or some combination of these.
  • This doesn't include MongoDB calls that just use save() for example... which is not recommended at all. Error traps are good when connecting to third parties whether they are local or remote. I'm not perfect either but I can get easily burned out on fixing these which is why I work in stages instead of all at once. Don't get paid for that! ;) :) Always fill out the arguments if known especially with aErr. That's a reason why it's done first in this coding style.
  • This was a very brief skim over the code... hopefully it wasn't overzealous or underzealous in code points... but they are comments to be addressed eventually. Living on four hours of sleep in 3 days isn't good so I'm taking a break not to mention a few days away from holiday days.

Applies to #430 and indirectly to #1548

Signed-off-by: Martii martii@users.noreply.github.com

* These are mostly comments in this PR
* Normalized a few more identifiers to their standards for easier grep'ing. I'm sure there's more.
* Some of these may be silent as intended... they should be denoted as such... like `fallthrough` for `switch` should be normally
* Some of these assume that AWS S3 and MongoLabs are perfectly connected and no issues... bad idea. This is what I was describing. We need [OpenUserJS#37](Graceful failure) whether it's a comment, a console message, a page, or some combination of these.
* This doesn't include MongoDB calls that just use `save()` for example... which is not recommended at all. Error traps are good when connecting to third parties whether they are local or remote. I'm not perfect either but I can get easily burned out on fixing these which is why I work in stages instead of all at once. Don't get paid for that! ;) :) Always fill out the arguments if known especially with `aErr`. That's a reason why it's done first in this coding style.
* This was a very brief skim over the code... hopefully it wasn't overzealous or underzealous in code points... but they are comments to be addressed eventually. Living on four hours of sleep in 3 days isn't good so I'm taking a break not to mention a few days away from holiday days.

Applies to OpenUserJS#430 and indirectly to OpenUserJS#1548

Signed-off-by: Martii <martii@users.noreply.github.com>
@Martii Martii added enhancement Something we do have implemented already but needs improvement upon to the best of knowledge. CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. labels Dec 21, 2018
@Martii Martii merged commit 35bd18b into OpenUserJS:master Dec 21, 2018
@Martii Martii deleted the Issue-430tagErrorProne branch December 21, 2018 13:05
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. enhancement Something we do have implemented already but needs improvement upon to the best of knowledge.
Development

Successfully merging this pull request may close these issues.

1 participant