New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add A FAQ #4852
Comments
I assume I can suggest one more common question, the one which I met today: I think it happens to almost all who tries to connect https://github.com/gaearon/react-hot-loader to the project where the I'm not sure that my solution is correct. And, actually, I would be much cooler if we can not pass any properties to the rendered component, as it's suggested in the Thanks for the router itself! Regards, |
was it removed? That information would be already more than nothing. I'm fine with parsing that by myself, but at the first moment I thought I just can't find it :) |
Because it bloated the library and made assumptions about how you wanted the query string parsed. querystring, qs, and query-string all parse differently, which may or may not integrate well with other parts of your system. We don't want to form an opinion on this and then force you to take a double-hit for including two query string libraries. |
thanks for the explanation, sounds good |
Closing because #4896 was merged. I have a draft with an answer to the |
I think that it would be beneficial if there was a list of frequently asked questions. The type of questions that can be answered by pointing the user to existing documentation or should be handled on StackOverflow, but still show up here.
The ones that I can think of off the top of my head are:
q. Why aren't my components updating
a. link to the blocked updates guide
q. Why don't my components render after refreshing?
a. This usually is because the dev is using
<BrowserRouter>
with a static websiteq. Why doesn't my application work when loading nested routes?
a. This usually happens when the bundled source in the script tag uses a relative path (
<script src='bundle.js'>
should be<script src='/bundle.js'>
)q. What happened to
location.query
a. ...
(I'm not sure any answer will satisfy some people, but at least give a basic explanation of why it was removed)
The text was updated successfully, but these errors were encountered: