| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Closes #646
|
|
|
|
|
| |
If the minOrder is 0, the previous code does not work. This code is now
doing the obvious stuff to change the order.
|
| |
|
|
|
|
| |
See https://github.com/meteor/meteor/issues/6162
|
| |
|
|
|
|
|
|
| |
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 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
|
|
|
|
|
|
| |
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()`.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
We need to use "function() {}" instead of the ES6 style "() {}" with
popup.afterCommit because we need the original value of "this" inside
the callback.
|
|\ |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
Replace the old (and broken) jshint + jscsrc by eslint and configure
it to support some of the ES6 features.
The command `eslint` currently has one error which is a bug that was
discovered by its static analysis and should be fixed (usage of a
dead object).
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This new draft saving system is currently only implemented for the
card description and comment. We need better a component
inheritance/composition model to support this for all editable fields.
Fixes #186
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Automatically display the overlay when the card details is opened
(previously we waited for the mouse to enter the card details panel)
* Improve the design of the minicards badges
* Change the minicard background when it is hovered or selected
* Removes unimplemented features links from the UI
* Fix the board canvas position when the sidebar is open (was hidden
behind)
Fixes #215
|
|
|