Feature request: Custom CDS names for rule "Use CamelCase for known CDS names"

[ConjuringCoffee]

Hi Jörg-Michael, would it be possible to somehow provide a list of custom CDS names to the rule "Use CamelCase for known CDS names"? Maybe an additional file that can be handled independently from the profile? 😉

[jmgrassau]

Hi ConjuringCoffee,

haha, I was literally waiting for this suggestion to come up, and you did it within less than 1 hour after the release!

Yes, this should be doable, and I already tried to consider this as a possible enhancement while implementing the current functionality.

My idea would be to

• specify a subfolder of the "profiles" folder (so it can be synchronized as part of team profiles), along with file prefixes for one or multiple text files containing custom view names or field names, respectively (e.g. "profiles/CamelCase/ViewNames.txt" and "profiles/CamelCase/FieldNames.txt")
• specify a format for these text files – probably simply "MyCustomFieldName\<linefeed>"
• allow each profile to activate or deactivate custom CDS names (but always using the same text files)

• prioritize these custom names between the "approved" ones and the "known" ones from SAP. So, if you have

  • "CompanyCode" approved at SAP
  • "Companycode" and "AnyFieldname" in your custom files
  • "AnyFieldName" known (but not approved) at SAP,

  then "CompanyCode" (from SAP) and "AnyFieldname" (from custom files) would override the other variants.

• maybe even provide some sample ABAP code for downloading this information from your SAP system (tables DD02B and DD03ND)

Would that make sense? Some open question include

• whether custom names should be checked against naming rules and filtered out if they violate them (e.g. with respect to allowed prefixes and suffixes, or if they start with a lower case letter like "anyFieldName"),
• what to do if custom files contain contradictory names (e.g. both "AnyFieldname" and "Anyfieldname")
• whether to prioritize personal custom files in %APPDATA% higher or lower than synchronized team custom files.

Kind regards, Jörg-Michael

[ConjuringCoffee]

Thank you for the quick and elaborate response! Your basic idea is sound, but to me it would be important to be able to have the settings independently from the profile. Imagine one of the following scenarios:

• An open source project wants to provide the ABAP Cleaner profile and the names of its CDS views (e.g. how I currently do it via my ABAP Cleaner Recommendation)
• A developer works for multiple customers and must therefore already manually switch between multiple profiles (because the ABAP Cleaner settings are saved independently from the workspace, see #211)

[jmgrassau]

Hi ConjuringCoffee,

just to be sure that I understand you correctly: Where and how would a user then configure the location of their fiels with custom CDS names? And once configured, they would always be valid, regardless of the selected profile?

Kind regards, Jörg-Michael

[ConjuringCoffee]

Hi Jörg-Michael, here's how I'd imagine it:

• I want to set up a combination of a profile and a CDS naming file for each of my ABAP projects.
• For each open-source project that works with different settings, I'd create a new ABAP project.
• Only a single CDS naming file would need to be "active" for each ABAP project.
• While profiles are typically shared as read-only files, the CDS naming files should be editable by everyone. It would be enhanced frequently by various new developments, so I can't imagine that to be handled by a central instance. I'd imagine some kind of command on a CDS view to "add all names to the CDS naming file".

Does that make sense? 😄

The whole thing relies on the possibility to have settings related to each ABAP project. Is that feasible?