-
Notifications
You must be signed in to change notification settings - Fork 44
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
ReportExtension prefixes not working in columns when ObjectNamePrefix contains a space #263
Comments
Edit: When I changed the settings - "CRS.ObjectNamePrefix": "ART CU ",
+ "CRS.ObjectNamePrefix": "ART CU", It does not loop around and just keeps the same, but I still think this issue should be addressed |
It's related to this AL issue: microsoft/AL#7057 |
It's also related to this, dashes are also giving errors: #272 |
@deerware have you tried out the new option to provide multiple affixes in the appsourcecop.json |
@pri-kise I have just tried it. It seems to be working fine now. Testing process:
The looping around is a separate issue which can simply be fixed the user. The main issue is fixed. Thank you for the fix. |
Hi,
Our ObjectNamePrefix contains a space, because we need to distinguish our global and customer projects, our current settings are:
A problem unfortunately comes with ReportExtensions, it does not format correctly when it comes to spaces.
becomes
I could understand that, but even if we were to use the
ARTCU
instead ofART_CU
, it still doesn't work because it doesn't recognize it's own formatting and just loops around, and the name is changed with each save, like so:I would propose that multiple accepted prefixes could be set, with the default being the first one, or, better yet, just don't do anything if the prefix meets the requirements of AppSourceCop.json
The text was updated successfully, but these errors were encountered: