Meteor 1.4 compatibility

[anthonyboutinov]

It looks like this package is now not fully compatible with Meteor 1.4.

I'm trying to use isActiveRoute/isActivePath in class attribute, and nothing happens.

In console, things like ActiveRoute.name('home'); work correctly.

I use iron:router in my project.

[Paku-]

Same for FlowRouter!

That's the a point I think ...
https://docs.meteor.com/packages/modules.html#CoffeeScript

[Paku-]

1.4 working solution (FlowRouter):

Template.header.helpers({
    'isActive': function (itemName) {

        if (FlowRouter.getRouteName() == itemName) {
            console.log(itemName + ' > Active');
            return 'active';
        }

        else {
            console.log(itemName + ' > none');
            return 'none';
        }

    }

});

<li class="{{isActive 'home'}}"><a href="#" class="menu-home">Start</a></li>

[pxljoy]

I've having a similar problem, also in 1.4.
Outlined in more detail here:

http://stackoverflow.com/questions/40438607/meteor-pkg-zimmeactive-route-errors-cannot-install-packages-various-other-iss

if I have zimme:active-router added to my packages list, I get this when > meteor

=> Started proxy.
=> Started MongoDB.
C:\Users\Pj\AppData\Local\.meteor\packages\meteor-tool\1.4.2\mt-os.windows.x86_3
2\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:190
      throw error;
      ^

Error: Extracted archive '/C/Users/Pj/AppData/Local/Temp/.tmpkxwy69' should only
 contain one entry

[ full dump here http://pastebin.com/raw/jSA9N3AF ]

My package list is as follows:

meteor-base@1.0.4             # Packages every Meteor app needs to have
mobile-experience@1.0.4       # Packages for a great mobile UX
mongo@1.1.14                   # The database Meteor supports right now
blaze-html-templates@1.0.4 # Compile .html files into Meteor Blaze views
reactive-var@1.0.11            # Reactive variable for tracker
jquery@1.11.10                  # Helpful client-side library
tracker@1.1.1                 # Meteor's client-side reactive programming library

standard-minifier-css@1.3.2   # CSS minifier run for production mode
standard-minifier-js@1.2.1    # JS minifier run for production mode
es5-shim@4.6.15                # ECMAScript 5 compatibility for older browsers.
ecmascript@0.5.9              # Enable ECMAScript2015+ syntax in app code
shell-server@0.2.1            # Server-side component of the `meteor shell` command

kadira:flow-router
kadira:blaze-layout
erasaur:meteor-lodash
mquandalle:stylus
fortawesome:fontawesome
spiderable
fastclick
raix:handlebar-helpers
aldeed:collection2
aldeed:autoform
accounts-ui
accounts-password
matb33:bootstrap-glyphicons
msavin:jetsetter
gwendall:auth-client-callbacks

I've removed zimme:active-router because with it I can't do anything.

[zimme]

So all my time on this project is in a es2015 re-write that will be release under a new name to allow for the community to take over maintenance. I'll split the package up in activeroute:core, activeroute:iron-router, activeroute:blaze etc. I hope to have this done in a week or so and I don't have time to try and fix this problem in the current package but I will happily accept a PR.

[pxljoy]

I'm hyped for that, Mr. Zimme!

[raphaelarias]

For now, here it is a global helper (note that isActivePath is only working with route names):

Template.registerHelper('isActivePath', (routeName, data) => {
if (FlowRouter.getRouteName() === routeName) {
return data.hash.class;
}
});

[zimme]

I'll have some time to work on my packages this week so I expect to release a RC next weekend

[isAlmogK]

Was this released?

[zimme]

Sorry not yet

[isAlmogK]

Any plans to update it anytime soon?

[zimme]

I have the core and the iron-router part done, I just need to finish up the blaze part and at that point I can release an alpha.

[isAlmogK]

Cool and this new version will support react? Please keep me updated

[zimme]

The new architecture will allow for better modularity, I'll probably only do activeroute:core, activeroute:iron-router (maybe activeroute:flow-router) and activeroute:blaze.

Then the community can create packages for whatever view layer and router they want.

But when using react most people are probably using react-router and I believe that the functionality this package provides is already present in that setup. However if you're using
react with flow/iron then you don't really need a activeroute:react package because I would
just use activeroute:core and use the javascript functions in jsx.

[isAlmogK]

Yea that would work, why don't you already publish core?

[zimme]

I need to verify that it actually works properly and I don't wanna publish a new version of something that isn't at least as complete as the previous version. Though I can live with publishing it with only support for one router and one ui.