Meteor was updated to 1.3.4.4, though we haven't modified the code base to
organize it around the new module system, we will still benefit from the
possibility of importing NPM packages dirrectly. From my tests, it also improves
the build time.
Also as https://github.com/meteor/meteor/pull/5841 was merged in Meteor 1.3.4.2,
\#385 is now fixed.
We updated the following packages in the process:
aldeed:collection2 upgraded from 2.8.0 to 2.9.1
aldeed:collection2-core upgraded from 1.0.0 to 1.1.1
alethes:pages upgraded from 1.8.4 to 1.8.6
arillo:flow-router-helpers upgraded from 0.4.7 to 0.5.2
blaze-html-templates removed from your project
cfs:http-methods upgraded from 0.0.30 to 0.0.32
cosmos:browserify removed from your project
cottz:publish-relations upgraded from 2.0.0 to 2.0.6
kadira:dochead upgraded from 1.4.0 to 1.5.0
kadira:flow-router upgraded from 2.10.1 to 2.12.1
kenton:accounts-sandstorm upgraded from 0.1.8 to 0.5.1
meteorhacks:fast-render upgraded from 2.11.0 to 2.14.0
meteorhacks:inject-data* upgraded from 1.4.1 to 2.0.0
meteorhacks:meteorx added, version 1.4.1
meteorhacks:subs-manager upgraded from 1.6.3 to 1.6.4
mquandalle:jade upgraded from 0.4.8 to 0.4.9
softwarerero:accounts-t9n upgraded from 1.1.7 to 1.3.4
tap:i18n upgraded from 1.7.0 to 1.8.2
templates:tabs upgraded from 2.2.0 to 2.2.2
useraccounts:core upgraded from 1.13.1 to 1.14.2
useraccounts:flow-routing upgraded from 1.13.1 to 1.14.2
useraccounts:unstyled upgraded from 1.13.1 to 1.14.2
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
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
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 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.
tmeasday:presence was doing unnecessary ping calls to the server every
5 seconds instead of using the status of the DDP connection (this
could save a fair amount of traffic in case of important server load).
I guess this change also fixes#221, but since no issue reproduction
was provided, it's difficult to tell.
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).
Bower build process was sometimes unpredictable and had unspecified
dependencies (git) that caused bugs (eg #164, #172). Meteor packages
have better integration with the meteor build system and ensure
deterministic build, the downside being that we have to maintain
wrapper of JS package just for the purpose of publishing in
atmosphere. Others are also struggling with this, see for instance:
https://github.com/MeteorCommunity/discussions/issues/14
Hopefully we'll have a better solution one day (official browserify
integration? Who knows.)
As a side effect the new release of perfect-scrollbar breaks the
style, this will be fixed in a later commit.
Fixes#172
The new version of meteor speeds up the reload cycle, which is super
valuable during the development. I also removed the "imply-everything"
"meteor-platform" package in favor of a more fined-grained package
selection.
This version also introduces ES6 support with transparent babeljs
transpilation. Most features are enable (with the notable exception of
ES6 modules) and this commit started to use them in places where a XXX
comment suggested it.
Motivations:
* Iron-Router foces us to use Tracker.nonreactive black magic in order
to avoid un-necessary re-renders;
* There is a community consensus (supported by some MDG members) that
the flow-router API is easier to reason about;
* The useraccounts now supports flow router (that was a blocking
element when I considered the switch ~3months ago)
On the server we use the Picker router, as encouraged by the Kadira
team (which develop both Flow and Picker routers).
In the current state of things there are some bugs related to the
missing Loading architecure. Previously onRendered callback where
always called when the data the component needed was available, now
we have to handle this ourselves, which we will in a following commit.
This includes a security fix in mquandalle:bower, and a new package
for useraccounts iron-router templates which forced us to move some
configuration function calls.
Use a custom build of jquery-ui with only the plugins we need (instead
of including everything).
Fix a tricky bug of conflict between Blaze reactive updates and
jquery-ui (which caused cards to sometimes disappear).
The user is now able to upload an avatar, and pick one in a list.
This functionality should eventually be abstracted in a community
package but we still need to work on a great public API. We rely on
collectionFS to manage uploaded avatars. We also removed
bengott:avatar which was trying to solve the wrong problem (namely
displaying the avatar, which is as simple as displaying an image), and
not a avatar system as it should be.
Gravatar support is coming (back) soon. We may also want to have a
list of default fun avatars the user can choose instead of uploading
its own one.
We now replace native scrollbar by custom ones on the list card (which
is required by the new ergonomics in the parent commit), but the
"scrolling engine", is still native, we just hide the scrollbar and
draw our own in HTML/CSS using the perfect-scrollbar package (from
bower).
This commit also implements component scrolling when certain actions
are performed, eg scroll to the bottom when the new card composer is
opened.
