Alex.Buchatsky

> Same here. Doesn't work on net6, doesn't even show @odata.context as it used to in core 3.1 Same issue. The @odata.context is missing even in the case of OData...

I've made a [pull request](https://github.com/berhir/AspNetCore.SpaYarp/pull/6) that introduces SpaDevelopmentServerOptions.PublicPath option which corresponds to devServer.publicPath option of Webpack Dev Server. If .csproj file contains ` /dist` only requests with the specified path...

There may be some use cases when a single redirect path is not enough. For ex. when several SPAs are launched from different Razor views. So, semicolumn-delimited lists with wildcards...

Workaround that worked for me: karma.conf.js ``` webpack: { // webpack configuration output: { path: path.join(__dirname, 'temp'), } ... } ```

It's easy - the author forgot to add "g" to Regexp . Driver.js: getSqlFromSqlTree: function(sqlTree) { ... // process where ... expr = expr.replace(/\?/g, getValuesSubstitutionStringFunc);

and I also had to modify executeBaton.cpp in order to accept bool values back to DB: void ExecuteBaton::CopyValuesToBaton(ExecuteBaton\* baton, v8::Localv8::Array\* values) { ... // boolean else if(val->IsBoolean()) { bool b...

...and, in order to accept "unassigned": // null if(val->IsNull() || val->IsUndefined()) { ...

Again, already implemented in my repository

More propositions for updating entities: 1. Setting "PATCH" as default HTTP method for updating entities 2. Providing an ODataService option for specifying the preferred HTTP method for updating entities to...

Again, all changes are already done in my repository, cannot create chained PRs