Closed lorensr closed 8 years ago
Did your test app have much in it, or just a call to configure
that you manually changed during testing?
This looks great @lorensr! I'll take a better look tomorrow. Test app was just a manual testing app.
tests don't work, waiting on https://github.com/meteor/guide/issues/401
actually probably a different problem: http://stackoverflow.com/questions/36855256/what-could-cause-an-onuse-package-to-not-be-defined-during-a-package-test
tests working, would you like to add to them?
production-ready packages have tests and changelogs 😉 😄 good thing we're past 1.3 and don't have to use tinytest! https://github.com/lorensr/login-links/blob/master/tests/client/connectionLogin.js
You're a star! I'm just finishing up some contract work and merging all this is next on my list.
Thanks! It was enough changes that I wouldn't publish until more tests are written or it's re-manually tested
Not ready to merge, I haven't tested yet. Probably even has syntax errors 😜
Changes are more intelligible if you look at individual commits.
Reloader.reload()
so we can keepreloaderWasRefreshed
accurate.launchScreenDelay
this
, and now it's easier to see what's going on at the top level at the bottom of the filetakes longer to read and understand than this:
a lot of readbility has to do with naming and structure (
handle
->launchScreen
). similarly, note how I extracted out pieces of code, or compound booleans, into functions with names that were descriptive enough that no comment was necessary.