These are chat archives for reactioncommerce/reaction

12th
Feb 2016
Aaron Judd
@aaronjudd
Feb 12 2016 00:55 UTC
@jshimko there goes your cover :shipit:
Brent Hoover
@zenweasel
Feb 12 2016 00:56 UTC
Ooops, was I not supposed to do that?
Aaron Judd
@aaronjudd
Feb 12 2016 00:56 UTC
lol - just kidding
Brent Hoover
@zenweasel
Feb 12 2016 00:56 UTC
phew
Mike Murray
@mikemurray
Feb 12 2016 00:57 UTC
lol
Spencer Norman
@spencern
Feb 12 2016 00:58 UTC
hah
Aaron Judd
@aaronjudd
Feb 12 2016 00:58 UTC
@zenweasel don’t you know we’re trying to be very secretive? shush!
Spencer Norman
@spencern
Feb 12 2016 00:58 UTC
‘stealth mode'
Aaron Judd
@aaronjudd
Feb 12 2016 00:58 UTC
yeah, that’s it.
Brent Hoover
@zenweasel
Feb 12 2016 00:58 UTC
Well, it was a secret to me until I saw you tweeted it last week
So if that’s that you mean by “stealth” mode….
Spencer Norman
@spencern
Feb 12 2016 00:59 UTC
I always thought stealth mode meant tweeting company secrets on the interwebs
Aaron Judd
@aaronjudd
Feb 12 2016 00:59 UTC
basically.. we are open stealth.
Spencer Norman
@spencern
Feb 12 2016 01:00 UTC
oooh, new category
Brent Hoover
@zenweasel
Feb 12 2016 01:00 UTC
inadvertently stealth
Aaron Judd
@aaronjudd
Feb 12 2016 01:01 UTC
ok… back to the code. almost there. (more like, start coding for today, but whatever)
Brent Hoover
@zenweasel
Feb 12 2016 01:01 UTC
:shipit:
newsiberian
@newsiberian
Feb 12 2016 04:00 UTC
@mikemurray, Hi, Mike, did you have an experience to insert reaction i18n functionality (translations) into react components? I've checked your code and so far I see only i18nPlaceholder placeholder usage.
Mike Murray
@mikemurray
Feb 12 2016 04:06 UTC
@newsiberian theres noting special for that yet. You'd have to pass in the translated text as a property. Ideally though you'd pass in i18nLabel="app.text" or something and the translation would be taken care of inside the component.
newsiberian
@newsiberian
Feb 12 2016 04:07 UTC
Thanks, I need to dig it more :+1:
Lukas Sägesser
@ScyDev
Feb 12 2016 08:15 UTC
@aaronjudd I needed aldeed:template-extension in order to inherit the helpers (fieldComponent) from productDetail template, but not replace the template.
Lukas Sägesser
@ScyDev
Feb 12 2016 09:05 UTC
So, do you think is this a good thing to do? Am I not breaking with the Meteor or Reaction way by doing this? No better way to do it?
I think I wanna do all my extension packages this way.
balsig99
@balsig99
Feb 12 2016 15:11 UTC

First of all Congratulations for Such a AWESOME Project
Hi I am magento developer, Last Year I switched to node.JS then I encounter with recation. I am totally fall in LOVE with your’s Project. It have too much potential to kick out major ecommerce Platforms exist today.
I have some Feature suggestions for reaction. I know your’s NINJA developer Team already know what is best for reaction. Maybe most of my suggestion already in development stage
Hope YOUR’s Development Team consider some of my HUMBLE Suggestions:)

  1. FOR MUTLIVENDOR MARKETPLACE
    • Internal Message- internal messaging system to the vendors dashboard which allows the vendor to communicate directly with their customers.
    • Live Chat- vendors can communicate with customers in real time(Most Suitable Feature for meteor based ecomerce)
    • Dedicated Dashboard- Vendor have separate dashboard with analytic tools for day to day sales.
    • STORE LOCATOR- sellers to display their store addresses on google map.
    • PRICE QUOTES- Customers request quotes from a vendor products
    • Favorite Vendor- This feature allows customer to add a vendor stores to his favorite shops list with in their profile.
    • VENDOR REVIEW- Allows customer to leave reviews for vendors after a purchase is made. Other customers will be able to see all reviews/ratings of vendors.
    • Vendor Specific Shipping Rates- Allows vendors to create and setup multiple shipping methods
    • CUSTOM SELLER HOME PAGE - Sellers can easily customize their store fronts using a graphical user interface
  1. TWO-Factor Authentication for Both admin and sellers using https://duo.com/

  2. AJAX FILTER for Products

  3. Color attributes for products That is ajax filterable.

  1. Aftership integrations for SMS Notifications and ease of order tracking to customers.

At last Many Many Best Wishes for Future of REACTIONCOMMERCE
Thanks ,Balsig

Aaron Judd
@aaronjudd
Feb 12 2016 15:38 UTC
@balsig99 :thumbsup: thanks for that feedback.. good ideas
@ScyDev aldeed:template-extensions package was developed for reaction. it’s good to use ;-)
balsig99
@balsig99
Feb 12 2016 15:39 UTC
welcome @aaronjudd
Hats off to all reaction developers for their hard work and innovations
Lukas Sägesser
@ScyDev
Feb 12 2016 16:09 UTC
@aaronjudd I meant about dynamically injecting template pieces into existing templates.
Aaron Judd
@aaronjudd
Feb 12 2016 16:11 UTC
oh sure, that’s fine.. might be a little fragile if the existing templates change, but otherwise it’s perfectly reasonable.
Lukas Sägesser
@ScyDev
Feb 12 2016 17:16 UTC
True. If core changes, extending packages have to catch up anyway. But still miles better than hacking core files and having to port every change with every release, I think.
M Bybee
@MBybee
Feb 12 2016 19:09 UTC
@balsig99 I would love to see some of those myself :+1: I'm waiting for R12 to be solid, then I have some stuff I'd like to work on too
Spencer Norman
@spencern
Feb 12 2016 22:18 UTC
@aaronjudd - with the move to v0.12 are you guys using BlazeLayout alongside flow router? Any React Components yet? Starting to look at migrating some of our packages towards 0.12 and trying to get a handle on everything that we will need to be updating
Aesop7
@Aesop7
Feb 12 2016 22:19 UTC
Hi All, I'm trying to add a link to the user dropdown. What is the best way to do it?
Mike Murray
@mikemurray
Feb 12 2016 22:29 UTC

@spencern React components, maybe not so much anymore. After meteor published their new guide with some examples on how to use Blaze templates that looked react-like (passing props and callbacks to components), we decided stick with blaze for our core components. And we are still going componentized: reaction-ui contains a bunch of simple blaze components textfield, button, tagItem, cards, etc alongside the new UI theme editor.

There may be some react components where it makes sense, but sticking with blaze for the most part.

And yes, we are using BlazeLayout under the hood.

Aaron Judd
@aaronjudd
Feb 12 2016 22:30 UTC
@Aesop7 if you add a registry entry, you can define {provides=“userAccountsDropdown", route=}
Paul Grever
@paulgrever
Feb 12 2016 22:42 UTC
Any suggestions/best practices for switching from Iron Router to Flow Router? Or any packages that been updated to FlowRouter that we can use as an example?
Aesop7
@Aesop7
Feb 12 2016 22:42 UTC

@aaronjudd I think that I'm doing something wrong... This is how I'm calling registerPackage

ReactionCore.registerPackage({
  name: 'testyMcTest',
  autoEnable: true,
  registry: [{
    route: "home",
    provides: 'userAccountDropdown',
    label: 'mylink',
    cycle: 4
  }]
});

and this is where I've defined "home"

  this.route("home", {
    template: "home",
    path: "/home",
    name: "home",
    layoutTemplate: "coreLayout",
    yieldTemplates: {
      layoutHeader: {
        to: "layoutHeader"
      },
      layoutFooter: {
        to: "layoutFooter"
      },
      dashboard: {
        to: "dashboard"
      }
    }
  });
Paul Grever
@paulgrever
Feb 12 2016 22:44 UTC
Also love that you built in a ReactionCore.pathFor to help migrate! Was worried about that.
Mike Murray
@mikemurray
Feb 12 2016 22:46 UTC
@paulgrever the main thing is that subscriptions are moved out of the router and into templates. Then refrence this style for how to subscribe: http://guide.meteor.com/blaze.html#smart-components
@Aesop7 is the link showing up in the accounts drowpdown at all?
Aesop7
@Aesop7
Feb 12 2016 22:48 UTC
not if I try to use a custom route... but I tried changing it to "account/profile" and it works
is it a permissions thing? Am I defining a custom route wrong?
Mike Murray
@mikemurray
Feb 12 2016 22:51 UTC
@Aesop7 testing this myself. one sec
Aesop7
@Aesop7
Feb 12 2016 22:54 UTC
thanks!
Mike Murray
@mikemurray
Feb 12 2016 22:58 UTC
@Aesop7 if the link isn't showing up in the dropdown its probably a permission issue. In the 0.12 branch I was able to add it to the menu, click and navigate to /home. I'm signed in as admin, so everything would show up anyway.
Spencer Norman
@spencern
Feb 12 2016 23:01 UTC
@mikemurray is there a good example package / package + branch that shows the best practices for setting up routes within reaction packages with the v0.12 context? We’re coming from the world of having a routes/router.js file in every package that we probably over-used (e.g. https://github.com/getoutfitted/reaction-advanced-fulfillment/blob/development/common/router.js)
Mike Murray
@mikemurray
Feb 12 2016 23:02 UTC

@Aesop7 The link will not show if the user doesn't have permission to see it. And if the package its in is enabled.

https://github.com/reactioncommerce/reaction/blob/development/packages/reaction-accounts/client/templates/dropdown/dropdown.html#L53

Aesop7
@Aesop7
Feb 12 2016 23:06 UTC
:+1: I can see it as an admin. So how/where do I add the permission level for users?
Mike Murray
@mikemurray
Feb 12 2016 23:10 UTC
Aesop7
@Aesop7
Feb 12 2016 23:15 UTC
@mikemurray I just saw the new routing... I guess maybe I'll try swtiching to v0.12 and then revisit custom user dropdown
did v0.12 switch to flow router or is it still using iron router behind the scenes?
Mike Murray
@mikemurray
Feb 12 2016 23:17 UTC
100% flow router
we namspeded it as ReactionRouter
Aesop7
@Aesop7
Feb 12 2016 23:19 UTC
cool. And I'm looking for permissions... are those done in "registerPackage" or within ReactionRouter?
Mike Murray
@mikemurray
Feb 12 2016 23:20 UTC
in the registerPackage
Aesop7
@Aesop7
Feb 12 2016 23:23 UTC
I'm looking for an example in the codebase.
Aesop7
@Aesop7
Feb 12 2016 23:37 UTC
Found it! But I'm still trying to figure out what the values should be in order to give all users access
  permissions: [
    {
      label: "Social",
      permission: "dashboard/social",
      group: "Shop Settings"
    }
Aesop7
@Aesop7
Feb 12 2016 23:59 UTC
@mikemurray I'm still lost on this one... As far as I can tell the registerPackage for "account/profile" is here but the only permissions being set in that file are for "dashboard/accounts" :confused: