Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Strex807yAhh, even though I am just reading this, I feel so angry at the at the devs. FFS GET YOUR **** RIGHT
-
Fuck, that's so shitty. Coming from python, I take good documentation for granted. I can't even think how I could've learned programming without proper documentation.
So, thumbs up for you. You solved it with sherlock holmes levels of wit. -
ebroda1857yI'm fully understand your rage about worse docu. I saw this myself too often.
But as you know better by now are you helping to correct and improve the docu? At least opening an issue in the project? 😉 With a Link to this rant? ^^
Related Rants
-
Paralax8To improve our user's "experience" I suggested to my boss to add a status page showing...well, the current sta...
-
Thaillie1A fly landed on my screen. I spend the last hour to try and train it to follow my mouse pointer xD
-
Brolls15Story time: At a precious employer. Hire shit-hot contractor. No technical test at interview stage because he...
I finally got Redux-Form’s `initialValues` to work! Wooooo~!
/giphy confetti cheering
It turns out I haven’t actually been doing anything wrong for the past week. I mean, I've been working on other things during that week, too, but I've been trying to solve this the entire time.
The cause? ReduxForm made a breaking change awhile ago (v5; we’re using v7) that prevents the `initialValues` prop from working if you decorate your form component in the wrong order. Many examples online are incorrect because of this.
Basically, the decorators `reduxForm` and `connect` do not commute:
Incorrect:
`reduxForm(...)( connect(..., {...})(form) )`
vs Correct:
`connect(..., {...})( reduxForm(...)(form) )`
But what really pisses me off is that the fucking documentation specifically fucking states that you may decorate your component IN ANY [FUCKING] ORDER.
/giphy that is [fucking] false
So, I've been following example after [fucking] example that either list these in the wrong order, or I just don't notice the different order because it doesn't matter. AND because of that NONE OF THE [...] EXAMPLES WORK.
ARGH.
I've been pacing around the office trying to figure this out for days. I've rewritten my code three times to try to solve this. I've written two workarounds for it only to rip them out and try again because they both broke some other part of the UX. (e.g. causing false validation errors after rerender)
just. hafhsldkjhgjkhagklwhsdjfkahslf. 😡
/giphy angry hades
You know how I discovered this?
I found it in a github ticket. One solitary, untagged ticket from October of last year. Not a single goddamn post anywhere else mentioned this. And the [...] documentation specifically [...] states the [...] opposite!
Bloody [...] hell.
but it finally works.
as;kgjhaekl;gahgjkdflssdafh.
I could scream.
undefined
incorrect documentation
bloody fucking hell
wasted time
redux-form
incorrect examples