The issue was introduced in 3b2eb0f but was only partially fixed (in
urgency) in 71b9a42. We sould have test to avoid these trivial
regressions! (I guess React will also yelp in this particular case by
removing the need to link the template and the "component", and thus
removing the possibility to break this link)
Fixes#434
- use an explicit "boards" domain: /api/boards/:boardId
- pass authToken as a request parameter: /api/boards/:boardId?authToken=:token
- in the future, same route can be used with authToken set in the Authenticate: header easily
Since bug #431 is due to publish-composite I tried to fix this package
and propose a pull request but the code was difficult to refactor. I
decided to use @cottz package instead which handled DDP messages in
the correct order.
Fixes#431
This is an alternative to drag and drop to move a set of selected
cards. This feature was available at the list level until I deleted it
in 5bdf91b, so it makes sense to add it back at the multi-selection
level.
This operation should now be handled using the multi-selection
feature, ie “select all cards” and then move them or click the
“archive selection” button. This new process add an extra click which
I consider reasonable enough for a relatively rare operation -- plus I
want to encourage mutli-selection usage.
Closes#390.
3stack:presence upgraded from 1.0.4 to 1.0.5
arillo:flow-router-helpers upgraded from 0.4.5 to 0.4.7
cosmos:browserify upgraded from 0.8.3 to 0.9.2
fortawesome:fontawesome upgraded from 4.4.0 to 4.5.0
kadira:blaze-layout upgraded from 2.2.0 to 2.3.0
kadira:flow-router upgraded from 2.9.0 to 2.10.0
meteorhacks:fast-render upgraded from 2.10.0 to 2.11.0
useraccounts:core upgraded from 1.12.4 to 1.13.0
useraccounts:flow-routing upgraded from 1.12.4 to 1.13.0
useraccounts:unstyled upgraded from 1.12.4 to 1.13.0
