-
Notifications
You must be signed in to change notification settings - Fork 29
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
Remove clientMutationId and use React Spa Template for .NET 6 #120
base: master
Are you sure you want to change the base?
Remove clientMutationId and use React Spa Template for .NET 6 #120
Conversation
.NET 6 has not been released yet. Is there so much difference that we cannot use the .NET 5 server for the SPA? It should be fine if the SPA itself is based on the .NET 6 template. |
It looks like .NET 6 is scheduled for release in November. Not that far away. |
Hi @Shane32! Only the todo spa app is based on .net 6. I think it is far easier to use this template than to manage the react app yourself (webpack). What do you think? |
Certainly don’t want to manage the spa setup but if the .NET csproj targets .NET 5 rather than .NET 6 most likely everything else (such as create-react-app, which does the webpack setup) can stay the same. |
|
Sounds fine. I can't push an updated package to nuget anyway. See #110 |
Fixed |
Finally! 🚀 |
@Shane32 I just made some changes based on this issue, #106