-
Notifications
You must be signed in to change notification settings - Fork 518
Update aspnet-webpack-react to React 15 #256
Conversation
Hi @geirsagberg, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution! TTYL, DNFBOT; |
@geirsagberg, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR. |
Thanks for this! Is the change to |
Only the package.json part is necessary yes. The type definitions caused a problem when building a second time, as they would be included as input files and therefore could not be written to. This is a separate issue from the version update, and also a problem with the other packages in the repo. I can separate the fixes into their own pull requests if you like, tomorrow. |
Thanks for clarifying. No need to modify this pull request - I'll just tweak the As for submitting a pull request containing the other bits, that's fine, but please provide more info on why it's necessary. Does it only become necessary because of something that's different in React 15 (and if so what)? Or have you always found it necessary? If the latter, I'd like to understand it better, because it hasn't been necessary in any scenario I've personally experienced. Thanks! |
I noticed after running
Excluding the Apropos, I see now that there is a new pull request #258 to upgrade to TS 2.0, which might make this a non-issue? |
Oh I see. Thanks for clarifying. What we've done in other projects (e.g., |
Ah yes, that would also do the trick :) |
Hmm.. I just tested the ReactGrid example using the version of |
* upstream/dev: Add ability to configure environment variables for Node instances, plus auto-populate NODE_ENV based on IHostingEnvironment when possible. Fixes aspnet#230 Rename PrimeCache to PrimeCacheAsync (keeping older name as obsolete overload). Fixes aspnet#246. Prerenderer now passes original (unescaped) URL to Node - fixes aspnet#250 In WebpackDevMiddleware, allow configuration of ProjectPath (implements aspnet#262)
Figured out the issue with ReactGrid; the problem was Griddle, not React 15 (I updated all npm dependencies to latest package version). I have also added |
Hi @geirsagberg, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution! The agreement was validated by .NET Foundation and real humans are currently evaluating your PR. TTYL, DNFBOT; |
@@ -5,14 +5,16 @@ import { fakeData } from '../data/fakeData.js'; | |||
import { columnMeta } from '../data/columnMeta.jsx'; | |||
const resultsPerPage = 10; | |||
|
|||
const fakeDataWithAction = fakeData.map(data => Object.assign(data, {actions: ''})); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In latest version of Griddle, nothing is rendered for a cell if data does not have a property matching the column name, so had to add an empty field "actions".
Excellent - looks great! Will merge soon. Thanks for this. |
@@ -38,5 +38,5 @@ export interface Reducer<TState> extends Function { | |||
} | |||
|
|||
export interface ActionCreatorGeneric<TState> extends Function { | |||
(dispatch: Dispatch, getState: () => TState): any; | |||
(dispatch: Dispatch<TState>, getState: () => TState): any; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch! Need this for my issue with TS2.0 PR & React as well.
node_modules/redux-typed/StrongActions.d.ts (16,16): error TS2314: Generic type 'Dispatch<S>' requires 1 type argument(s).
BTW I noticed a small issue with KoreBuild not building the sample projects correctly due to the sample projects being in a lower subdirectory (e.g. I worked around the issue locally by changing the glob manually in the downloaded |
Root dotnet restore also doesn't run webpack vendor files for each project which would make developing on the repo easier too, not sure if that's related! |
Thanks for cleaning up those parts of the build script too. This is now merged :) |
Hey @SteveSandersonMS I don't think this PR got merged somehow, it looks like none of the code is in the Repo (just tried searching for it, the old code is still there) Not sure why? For example I need
|
Fixes #255.