-
-
Notifications
You must be signed in to change notification settings - Fork 301
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
Example "Custom renaming with epft.renaming.json" in documentation doesn't work as described. #364
Comments
Is it not just a typo: "NewName": "CourseOffering", ?? Otherwise, please provide a CREATE TABLE script and a json file, and I will have a look. |
CREATE TABLE script:
Jason File:
Result after reverse engineering: Result i would like to get: ButtonBerechtigungEN is the plural in german. Greetings from Switzerland. |
There is currently no non-English pluralization, so this is not at all possible. |
Maybe this PR would solve your issue, but I have not had a closer look at it yet. #317 |
Ok thanks for your help i will find another solution. But keep in mind then your documentation is not correct. becaause the efpt.renaming.json sample file: which you provide here will not lead to the shown result:
the results then would actualy contain an 's' in the typename aswell: |
Oh and did you maybe forgot my 2. Question?
|
Thanks, I have removed all the "s" endings from the sample. Re your second question: Potentially, if I decided to use/merge the above mentioned PR |
Hi there
In your documentation in the section "Custom renaming with epft.renaming.json", you write following:
But if i use your efpt.renaming.json sample file i get this
Result i get:
public virtual DbSet< CourseOfferings> CourseOfferings { get; set; }
Class and Filename: CourseOfferings and CourseOfferings.cs
Result i would like to get:
public virtual DbSet< CourseOffering> CourseOfferings { get; set; }
Class and Filename: CourseOffering and CourseOffering.cs
In my case i dont use the function 'Pluralize or singularize generated object names (English)' because we dont use english properties.
Questions
Thanks for your help!
Further technical details
EF Core Power Tools version: 2.4.0.0
Visual Studio version: (Visual Studio 2019 16.4.2)
The text was updated successfully, but these errors were encountered: