pluralize | Pluralize or singularize any word based on a count | Internationalization library

Use pluralize (and probably don't use the older style % formatting):

If you have a look at the official documentation - you'd see:

Scaffold-DbContext

Parameters

...

• Tables - The tables to generate entity types for. If this parameter is omitted, all tables are included.

...

• NoPluralize - Don't use the pluralizer. Added in EF Core 5.0.

So yes - both of your requests can be handled with parameters to Scaffold-DbContext - just consult the docs!

As explained in this GitHub issue

A few suggestions:

• You should either choose between a full callback approach and a full promise approach
• Don't mix async / await with .then syntax when you can avoid it

This article has helped me. The solution was to set LANG=en in shell and then to run XAMPP from this exact shell.

Finally, to get gettext working in XAMPP, you need to set the LANG attribute on the XAMPP shell before you fire up the XAMPP Control Panel every time you want to use XAMPP.

The XAMPP shell is right inside the install folder, which means it should be at C:\xampp\xampp_shell.bat for most people. Run it (preferrably as an Administrator), and type the following:

set LANG=YOUR_LANGUAGE_CODE

YOUR_LANGUAGE_CODE needs to be replaced with the appropriate language code of your localisation. For example, if my localisation was for Simplified Chinese, it would look like this:

set LANG=zh_CN

Once done, use the following command to open the XAMPP Control Panel from the shell.

xampp-control

You really don't have to do much to get forms to work with nested routes.

When you're using form_with it passes the arguments to the polymorphic route helpers which will compact the array when trying to find a corresponding route:

Try this in app/views/users/new.html.erb

<%= render 'shared/error_messages', user: @user %>

If it's a shared partial, maybe make the instance variable generic rather than @user also. That way it can be reused and less confusing later.

With some help from Michael Koper, we were able to sort this out. The controller methods were missing status: :unprocessable_entity on the format.html statements. So changing:

format.html { render action: "new"}

to

format.html { render action: "new", status: :unprocessable_entity }

Solved this issue.

never extends everything. To get a feel for why, it may help to think of types as being sets.

Consider the code A extends string. If we're thinking in sets, then this means "A is a subset of string". string is the set of all possible strings (so "a", "aa", "aaa", etc). A type like "a" | "b" extends from string, because the set with elements "a" and "b" is a subset of the set of all possible strings. A type like "a" | 2 does not extend from string, because it has an element (2) which string does not have, making it not a subset of string.

So what set is never? It's the empty set. There are no values in the set. This is why it's impossible to assign to never, because no value exists which work for it. But because it's the empty set, it is, by definition, a subset of every other set. Therefore, it extends from everything.

Finally if I want the ts compiler to complain when input is invalid what is the correct pattern to use ?

You won't be able to ban never from this type, but i'm not sure why you'd need to. While the type Pluralize is legal, it's not possible to construct something that matches that type. For example, if i had a function like this:

Issue #22475 Detect simple join tables in reverse engineering and create many-to-many relationships and #26820 Optionally bring back join tables on scaffold db in EF Core 6 were opened for this. Apparently there's no direct way to map join tables, but workarounds are available (and described in the second link).