| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
amadilsons-userSelfRemove
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| | |
https://github.com/AlexanderS/wekan into AlexanderS-feature/link-to-shortcuts
|
| | |
|
|\ \
| | |
| | |
| | | |
umbertooo-fix-quit-board
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
|/
|
|
| |
The name of the profile field was changed log ago. This fixes the
remaining wrong references.
|
|
|
|
| |
This commit also tweak the code style following backward-incompatible v2 rules.
|
|
|
|
|
|
| |
This code was duplicate with the name we use to `register` the
component. A update of blaze-component removed the need to duplicate
this declaration.
|
|
|
|
|
|
|
|
| |
I imagine blaze-component changed their Mixins API since I written
this code. We need some tests to avoid this kind of regressions when
updating dependencies!
Fixes #420
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This bug was introduced with the introduction of fast-render in
41b23f8. With fast-render data is available instantly after the page
logging, but calls to `Meteor.userId()` still return `null` as the
user isn't authenticated on the DDP channel yet (previously the data
was loaded on DDP after user authentication). Which mean that we know
need to reactively activate Drag and Drop on user log in.
I'm not sure why I was not able to reproduce this bug outside of
Sandstorm.
Fixes #453
|
|
|
|
| |
Closes #399
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
to quit
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since 07cc454 (ie the switch to Meteor 1.2) we includes the `es5-shim`
polyfill to support methods like `Array.prototype.forEach` in a
consistent way across all supported browsers (IE8+).
MDG recently released a blog post recommending the use of these native
methods instead of underscore [0]. We know follow this recommendation.
This commit also favor some ES6 features (argument defaults,
destructing assignment) in places where we didn’t use them.
[0]: http://info.meteor.com/blog/es2015-get-started
|
|
|
|
|
| |
This change includes method renames and others UI related packages
updates.
|
| |
|
|\
| |
| | |
sidebar: Filter archived cards/lists for current board
|
| |
| |
| |
| |
| | |
The archived items should be filtered for the current board or else you
will get a global list of all archived items on all boards.
|
|/
|
|
|
| |
The removeMemberPopup was missing the required helper to get the user and board
information and the user profile field is called "fullname" and not "name".
|
| |
|
|\
| |
| |
| |
| | |
Fix multiselect toggle logic
This bug was introduced in 45b662a
|
| |
| |
| |
| |
| |
| | |
If every element already has the label/member, we do not need to add it
but it should be removed and if every element does not have the element,
we should add it.
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
This bug was introduced in e964fbb5.
Fixes #295.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit uses a new package that I need to document. It tries to
solve the long-standing debate in the Meteor community about
allow/deny rules versus methods (RPC).
This approach gives us both the centralized security rules of
allow/deny and the white-list of allowed mutations similarly to Meteor
methods. The idea to have static mutation descriptions is also
inspired by Facebook's Relay/GraphQL.
This will allow the development of a REST API using the high-level
methods instead of the MongoDB queries to do the mapping between the
HTTP requests and our collections.
|
| |
|
|
|
|
|
|
| |
Fixes #288
Fixes #289
Fixes #290
|
|
|
|
| |
Fixes #265
|
|
|
|
| |
Fixes #280
|