Chris L.
Chris L.
I suggest using the way described in the Wiki. Your outer most container is responsible for routing and provides all the routes. The route component itself is just a component...
Yes, that was me replying ;-) I will try to set up an example in the next couple of days to illustrate this.
This is just a short log of my experimentation with react-router, skip to the bottom for source link. # Abstract: In this example the user will be shown a link...
I would not say it is the _only way_ (especially in the JS universe ;-), there are multiple routing solutions: - [react-router-redux](https://github.com/reactjs/react-router-redux) (like react router but also allows for redux'...
Give me a couple of days to look into this, might have to do with ast parsing.
Alright, this seems to be multiple issues at once. The spread operator **...** seems to be a problem when parsing the abstract syntax tree. So @Primajin instead of ``` module.exports...
OK, so both on you are on mac. Interesting. I am on Linux and get an error -_- will be awesome to debug :-D I guess I should be able...
Not sure if I understand the question. This module is intended to be used in schema files, so I would say yes. But maybe you can tell me your specific...
Good catch. Thank you. I am not sure if it would not be better (and cleaner) to refactor the code so it is compatible with the newer version. I will...
Oh, great you did some research. In this case freezing the version as you suggested is the only way to go. Quite a bummer, I have to admit :-/