The upgrade in 9ef8eba introduced a breaking change.
peerlibrary:blaze-components downgraded from 0.16.2 to 0.15.1
peerlibrary:data-lookup removed from your project
Fixes#471
aldeed:collection2 upgraded from 2.5.0 to 2.8.0
aldeed:collection2-core added, version 1.0.0
aldeed:schema-deny added, version 1.0.1
aldeed:schema-index added, version 1.0.1
aldeed:simple-schema upgraded from 1.3.3 to 1.5.3
cosmos:browserify upgraded from 0.9.2 to 0.9.3
mdg:validation-error added, version 0.2.0
meteorhacks:subs-manager upgraded from 1.6.2 to 1.6.3
peerlibrary:blaze-components upgraded from 0.15.1 to 0.16.2
peerlibrary:data-lookup added, version 0.1.0
useraccounts:core upgraded from 1.13.0 to 1.13.1
useraccounts:flow-routing upgraded from 1.13.0 to 1.13.1
useraccounts:unstyled upgraded from 1.13.0 to 1.13.1
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
For one `devel` is not stable and it's better to use the last released
version which is always in sync with `master`. Also Scalingo currently
doesn't support running "non-standard" versions of the Meteor build
tool such as the one we are currently using in `devel`.
The layout issue was related to the lack of autoprexing for CSS
properties. c69f993 did improve the reload time significantly but for
that I had to replace `mquandalle:stylus` by the core `stylus`
package. Unfortunatly it is currently difficult to run an autoprefixer
with the core CSS compilers (as reported in
https://github.com/meteor/meteor/issues/5219).
So instead we rely on `nib` which transparently define some mixins for
autoprefixing, the only restrictions being that we have to manually
`@import 'nib'` on top of stylus files.
Fixes#461
Meteor support that use case for us, we don't need to implement our
own validate strategy on top of that. This was also discussed as part
of the #454 review.
The bug comes for 9154b06 which this commit partially reverts. The
synchronization between the user document profile and the Sandstorm
HTTP headers is still not perfect. Having a clean model may requires
the `accounts-sandstorm` to expose a hook to modify the user document
just after the `services.sandstorm` credentials are updated.
Fixes#460
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
The bug comes for 9154b06 which this commit partially reverts. The
synchronization between the user document profile and the Sandstorm
HTTP headers is still not perfect. Having a clean model may requires
the `accounts-sandstorm` to expose a hook to modify the user document
just after the `services.sandstorm` credentials are updated.
Fixes#460
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
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.
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
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
Maxime Quandalle