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
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.
We now use the `preferredHandle` exposed by Sandstorm as source for
the username and append a number if the username is already taken
since we need to ensure username uniqueness (eg 'max', 'max1', 'max2')
Fixes#352
This commit stands on the initial support implemented in #342. We now
avoid error-prone parsing step by adding the member or the label
directly to the card object.
We also added support for `Tab` to completion on our textComplete
component.
Closes#342
The previous users accounts templates configuration only happened on
the client, which was wrong and caused some bugs, for instance an
invalid URL was generated in the reset password e-mail.
Fixes#297
This version includes a more complete selection of ES2015 polyfills
that I started used across the code base, for instance by replacing
`$.trim(str)` by `str.trim()`.
