Error: >reactiveTable.show< >reactiveTable.rowsPerPage< >reactiveTable.page< >reactiveTable.of< 1 about reactive-table HOT 11 OPEN

It seems to be a problem with the just-i18n dependency

from reactive-table.

yes, that sounds like the problem. is just-i18n in your smart.lock?

from reactive-table.

I am also having this issue, 'just-i18n' is in my smart.lock, I tried v0.2.3 & the latest (0.2.4) it did not change, still having same issue.

  "just-i18n": {
    "git": "https://github.com/subhog/meteor-just-i18n.git",
    "tag": "v0.2.3",
    "commit": "494c5a1efb07ccb498e9a74283817fdddcd528c4"
  },

from reactive-table.

I haven't been able to reproduce this, but I'll look into it if someone can point me to an example app with the same issue.

from reactive-table.

I got this error too. After some digging, I believe it's because I'm using another package (accounts-entry) that also depends on just-i18n. I'm thinking the problem is that you can only call i18n.map() once.

from reactive-table.

Thanks, I can reproduce it using accounts-entry. The problem is actually that accounts-entry is using a different translation package called accounts-t9n, which overwrites the i18n helper and breaks just-i18n. They say this is for backwards-compatibility with just-i18n, but it doesn't actually work since it doesn't let you use i18n.map. I'll create an issue in that package.

from reactive-table.

I confirm the issue when both packages are used together and will try to avoid this in the future. For a quick fix you can try to exclude just-i18n in smart.json and translations should work as expected.

from reactive-table.

I don't think excluding just-i18n would fix the problem in this case, since the translations are defined with i18n.map. Maybe accounts-t9n could set i18n.map to t9n.map, and export i18n though...

from reactive-table.

You are right, you would have to call the method 'map' on the T9n object.

Maybe accounts-t9n could set i18n.map to t9n.map, and export i18n though...
There is no control over the load order of the packages so it would only work sometimes, also I would introduce more deprecated code.

from reactive-table.

I don't want to add a dependency on accounts-t9n to reactive-table (unless someone can point out any advantages over just-i18n), but for anyone who wants to use both packages, a workaround is to add a translation to T9n from your app, e.g. for English:

T9n.map('en', {
  reactiveTable: {
      filter: 'Filter',
      show: 'Show',
      rowsPerPage: 'rows per page',
      page: 'Page',
      of: 'of'
  }
});

from reactive-table.

I just removed the i18n helpers from t9n so there shouldn't be any more collisions between the module. I guess you can close this issue.

from reactive-table.