Closed Marvinnnne closed 3 months ago
The issue is that when it attempts to parse the letters into works, the first word it finds is Tea, and then it tries to parse the rest, and fails miserably. Good news is you can fix this with configuration. If you want it cased as "Accountea" and "Appointmentea" then you just need to add "Accountea" and "Appointmentea" as custom words:
if you want some other casing, use the Token Capitalization Override and enter the exact casing you want, maybe "AccountEa" or "AccountEA"
Maybe i'm doing something wrong or I didn't understand but I put accountea and appointmentea in camel case custom word, remove namespace, and add AccountEA in token capitalization overrides but, the file name is still Account or Appointment.
What did I do wrong ?
I add _EA at the end of each class I need. It seems working.
Ah, the Entity Class name override may not utilize the casing logic since you're explicitly defining the value, In that case you can remove the changes you made to the tokens and custom dictionary and just case it how ever you'd like in the class name overrides.
Tool and Version EarlyBoundGenerator V 2.2024.2.1
Describe the bug I try to generate a specific name for my entity file because my plugin have the same name and it make difficult to read code. The CamelCase is broken. Maybe there is a parameter to add a suffix or prefix to generate files ?
See attachment