These are chat archives for reactioncommerce/reaction

4th
Dec 2015
Aaron Judd
@aaronjudd
Dec 04 2015 00:15 UTC
@serapath that’s a mystery at the moment (it’s a TBA feature, coming soon)
newsiberian
@newsiberian
Dec 04 2015 05:41 UTC
Hi, everyone, I've faced with funny behavior then debugging. Almost every insert, update operation repeats twice, sometimes thrice. Is this expected behavior for debugging mode?
Aaron Judd
@aaronjudd
Dec 04 2015 05:54 UTC
no, that doesn’t sound normal
client or server?
newsiberian
@newsiberian
Dec 04 2015 05:56 UTC
server side. this happens for a long time with me
Aaron Judd
@aaronjudd
Dec 04 2015 05:57 UTC
doesn’t sound right to me, but maybe if you are running tests (velocity, jasmine?) as well - then I would expect it
newsiberian
@newsiberian
Dec 04 2015 05:58 UTC
no, just meteor debug
newsiberian
@newsiberian
Dec 04 2015 06:03 UTC
btw, @aaronjudd, how to work with core now? Should we do changes in reaction/package/reaction-core from now?
Aaron Judd
@aaronjudd
Dec 04 2015 06:19 UTC
yes, switch to just using the reaction repo, and not any of the other repos.
Spencer Norman
@spencern
Dec 04 2015 20:52 UTC
What was the reason behind the switch from independent repos for reaction packages to all-in-one?
Aleksei Mironov
@alexmironof
Dec 04 2015 20:56 UTC
Sorry, I've missed everything... Is it using git submodules now?
Mike Murray
@mikemurray
Dec 04 2015 20:57 UTC
No, we merged the packages into "reaction"
Aleksei Mironov
@alexmironof
Dec 04 2015 20:59 UTC
Oh I see, thanks @mikemurray I'll try to merge it on top of my work
Mike Murray
@mikemurray
Dec 04 2015 20:59 UTC
We did it to make it easier to "hit the ground running"
Spencer Norman
@spencern
Dec 04 2015 21:00 UTC
Ok, what’s the best-practices for merging 0.10.x updates into an existing deployment? Just nuke and start over?
Aaron Judd
@aaronjudd
Dec 04 2015 21:00 UTC

Generally just to make life easier, and clearer.

  1. Maintaining and publishing all the packages and keeping them in sync working for testing was already getting to be very tedious.
  2. It's more legible,clear to new devs if the code is in the packages dir rather than a magical package manager elsewhere.
  3. make it easier to customize at the app level
  4. We'll still publish to Atmosphere, and that's still a way to get updates.
  5. Testing.. testing.

We still have packages that are not in the app level (payments, etc). reaction pull (aka bin/clone-packages.sh) is now smart enough to pull external packages in to your packages dir, without conflict with local packages.

Spencer Norman
@spencern
Dec 04 2015 21:01 UTC
oh, nice - re clone-packages.sh
Aaron Judd
@aaronjudd
Dec 04 2015 21:02 UTC
if you have been using the /packages dir, you should be able to just do “reaction pull” and be good to go. you still have to pull the reaction repo as well (wonder if that should be included in that command)
however- the nuke option that I’ve done a few times -> rm -rf packages/* && git pull & git reset —hard HEAD
but only if you are nuking.. you really don’t need to
everything should just play nicely - and from now on your PR/commits,etc will go to the reaction repo
Aaron Judd
@aaronjudd
Dec 04 2015 21:09 UTC
if you have straggling stuff you want to merge from an old clone of one of the previous package repos google “git subtree” to merge it into the current directory. @kefirchik - no submodules, we’re pulled in via subtree… but disconnected the remotes
Mike Murray
@mikemurray
Dec 04 2015 21:10 UTC
Also, theres a significant change to the theaming. Theres no more reaction-bootstrap-theme package. Now only reaction-core-theme and reaction-default-theme
And we're now using the cross package less imports
Aleksei Mironov
@alexmironof
Dec 04 2015 21:28 UTC
Thanks @aaronjudd ! I'll check it out tomorrow
Aaron Judd
@aaronjudd
Dec 04 2015 21:29 UTC
:thumbsup: working through issues still, but honestly this is the release that 0.9 should have been ;-)
Spencer Norman
@spencern
Dec 04 2015 21:29 UTC
:+1:
Aleksei Mironov
@alexmironof
Dec 04 2015 21:33 UTC
:+1:
Israel Ortiz
@soyisraelortiz
Dec 04 2015 23:53 UTC
after 1 week, still cant figure out the issue with the paypal payment not completing, have anyone here had the same problem? and if so how did you solve it? i see this messages on the console consolerror