Peter
Peter
Looks like this is in progress in #100. Hopefully that can get merged quickly.
Also this happens when you have optional params `/page/:sub?` doesn't match `/page`
Any plans on merging this? Would be super helpful instead of having to manually enter the changes in whenever I install it.
Just tested and it looks like its cleared all of the conflicts that I was having. Thanks @developit!
For future reference, extending multi-namespaced aspects is weird (see #1714 ). For @kuhe: Easiest to do: ```typescript // global.d.ts declare namespace preact.JSX { interface IntrinsicElements { [tag: string]: any; }...
@kuhe You have to make sure to include the file in your `tsconfig.json` file. ``` { "compilerOptions": ... "include": [ "src", "global.d.ts" ] } ``` Something like the above.
Strange, it seems as though the behaviour has changed since I last looked into this. Investigating further!
Unfortunately, [declaration merging of namespaces in namespaces is not really supported](https://stackoverflow.com/questions/30357634/how-do-i-use-namespaces-with-typescript-external-modules) by typescript.
I'm not sure if this should be marked as a bug, or more of a gotcha that people should be aware of. EDIT: Further down in the post there is...
It would be great if this could be looked at again. Currently using contextType does not set the type of context in a class. It does set the proper type...