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
First draft for Support of multiple Prefixes #254
Conversation
@waldo1001 I would really appreciate if you give me some feedback on this pullrequest. This PR is related to the issue #263. |
My focus was more regarding field Names in Table Extensions or Columns in Report Extensions. |
Makes totally sense. Do know that multiple affixes is not possible anymore for partners - just old partners (like us?) might have multiple.. . We simply switch off auto-suffixing because of this and let the codecop handle it :(. But sure - let's see what you can come up with ;-) |
52d1a42
to
0f19e2d
Compare
@waldo1001 it took some time, but now I updated my code to make use of the AppSourceCop.json Looking forward to feedback. |
This is a first draft to support multiple prefixes.
Right now I added the feature only for table extensions fields.
But this can easily added for the other extension objects.
I was tryin to create a solution for issue: #151
It's not perfect, but I could work as temporary solution.
@waldo1001 do you have any plans and time to work on improvements of prefix handling or would accept the solution that is proposed with this Pull Request.
@christianbraeunlich you do seem to have some experience with npm.
Do you know how I can disable that the yarn.lock is updated and that yarn.lock is used instead of package-lock.json for this repository?