You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 12, 2020. It is now read-only.
I found the examples a bit tricky to read, I suggest improving them as follows:
Follow Hyperapp's style: 2 space indentation, bracket spacing, double quotes, avoid _ for paramless functions
Avoid cryptic/shortened variable names
Use named params for state, actions & view for readability
Shorten shuffle algo with destructuring assignment
For add, always place the new message at the beginning of the array so it appears on top - it's confusing having it appear randomly in the order (to me)
Styling could also be enhanced to make it prettier 😜
(well... all except the 2-space-indent rule. It will be 4 spaces as long as the examples are in my codepen account 😉 . But actually that brings up another question: perhaps it would make sense to move the examples to the hyperapp-account since the hyperapp org owns this repo 🤔. If that's decided, then yes definitely I should follow the style as the other examples. Also, the css should be updated )
Thanks also for exemplifying what you meant with by rewriting the Toasts example! I'll get to work on it, but it may not be this week. I have other things ahead in the backlog.
I found the examples a bit tricky to read, I suggest improving them as follows:
_
for paramless functionsadd
, always place the new message at the beginning of the array so it appears on top - it's confusing having it appear randomly in the order (to me)Here is Toasts:
The text was updated successfully, but these errors were encountered: