| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
As discussed in #370 and announced in the official Eslint-meteor
plugin repository (https://github.com/dferber90/eslint-plugin-meteor),
it is recommended to not use this plugin anymore has the author has it
is currently broken and the author has abandoned it.
|
|\ \
| | |
| | | |
optimize login form layout & css
|
| | |
| | |
| | |
| | | |
Fixes #448
|
| | |
| | |
| | |
| | | |
v0.4.7 was bugged, see https://github.com/mquandalle/meteor-jade/issues/195
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Following a valuable comment from @Slava [0], this commit improves the
build and the reload time of Wekan. It does so by implementing the
following changes:
* Upgrade the meteor build tool to a version which includes a fix to
an issue with the caching of the dependency resolution [1]. This fix
will be included in Meteor 1.3, so we won't have to use a
"special release" anymore;
* Change the stylus package from `mquandalle:stylus` to `stylus` as we
don't use the libraries included with my (mquandalle) version like
Jeet or Rupture, and the core package implement the new meteor build
plugin API with caching. The generated CSS file is slighly different
mostly mostly because we miss some autoprefixed values but even
until meteor-core figure out a good way to configure CSS
autoprefixing, the benefits (better compile time) outweights the
cons. For record I attached a diff in the generated style [2];
* Upgrade `mquandalle:jade` to a version that implements the build
plugin caching correctly.
These 3 changes decrease the reload time of about 50% on my computer.
[0]: https://github.com/meteor/meteor/issues/5269#issuecomment-166422201
[1]: https://github.com/meteor/meteor/pull/5747
[2]: https://gist.github.com/mquandalle/e95198626767b56fc63a
|
|/
|
|
| |
Closes #425
|
| |
|
|
|
|
|
|
| |
See the following discussion for rationale:
https://github.com/wekan/wekan/issues/113#issuecomment-163039089
|
| |
|
|
|
|
| |
Fixes #449
|
| |
|
|
|
|
| |
Fixes #302
|
|
|
|
| |
Closes #399
|
| |
|
|
|
|
| |
Fixes #433
|
|
|
|
|
|
|
|
|
|
| |
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
|
|\
| |
| |
| |
| | |
Export a board to JSON
Fixes #396
|
| |
| |
| |
| |
| |
| | |
- 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
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \ |
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
fix board header issue
|
|/ / / / |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This PR improves the UI on devices or windows with small screens.
Fixes #75
Fixes #437
|
| | |/ /
| |/| | |
|
|\ \ \ \
| |_|_|/
|/| | | |
One click deploy to Scalingo
|
| |/ / |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| | |
The buttons in the board header were not click-able anymore.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This commit also provide a way to escape the Shorcuts page on
Sandstorm.
|
| |
| |
| |
| | |
Fixes #277.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|