JavaScript Fatigue

[ffxsam]

How can we replicate the functionalities within Meteor using getMeteorData()?

You may wanna check this package out. It covers both Flux and Redux patterns.

[JDumont]

One of the most helpful threads/conversions/dialogues I’ve ever read about Meteor.

To OP: Your post did more to address my concerns about the churn rate of the NodeJS ecosystem and how that’s creeping into Meteor than any whining post from a frustrated developer, or any cloak-and-dagger statement from MDG.

Thank you!

[ciwolsey]

Redux has definitely made my life easier, if only for the great redux-forms which makes forms a breeze. Watching upcoming tools and understand what they solve is important. Don’t go blindly learning a tool if you don’t know why you would need it.

[korus90]

if you then run jQuery to trigger an event like so:$(’#my-input’).val(‘new-value’).trigger(‘input’);

You shouldn’t really be using jQuery with React though. You can use jQuery but it’s far from recommended, since React likes to take full control of the DOM.

You’d be better off with this markup:

<input id="my-input" type="text" name="myInput" onChange={this._onChange} />

and this JS:

event.target.myInput.value;

[hellogerard]

…you could make one Reactive-Dict, save it to a global like appState, and then use getMeteorData to watch any keys.

You can either set the data the normal way, or if you’d like you could create a file called ‘actions’, create a normal function called createPost and then from your view, pass in form data to createPost, which takes all of the mutation logic out of the view and moves it into a single place actions.

I’m in the middle of evaluating Redux, but for awhile now, this is exactly how I’ve used the “Flux” pattern. The mechanics described above is pretty much implemented in this package (but there are others): https://atmospherejs.com/woody/flux

[workman]

It sounds like there’s a larger paradigm problem going on. You really shouldn’t need to trigger an input with jQuery like that. If you could provide more info of the use case i’d be happy to check it out.

I trigger events during some of my automated testing. Like I said, I fixed it by making my testing framework smart enough to do it their way if it’s a react component I’m testing, but it’s annoying that it didn’t just work.

[SkinnyGeek1010]

I trigger events during some of my automated testing. Like I said, I fixed it by making my testing framework smart enough to do it their way if it’s a react component I’m testing, but it’s annoying that it didn’t just work

Oh, I see… I mis-read and thought you needed to do that in production. I’ve had really good luck with webdriver based tools like Chimp or Capybara. I’ve tinkered a bit with the React test utils but they’re pretty low level.