Use Case: Adding Feature

[lvanvugt]

The following flowchart shows the use case:

Exceptions

• Non-alphabetical or non-numerical characters should not be ported to test codeunit name
• As AL codeunit names have a max length of 30 characters we should restrict the length of feature description to this length for the time being
  • I suggest to build logic that checks allowed length in Scenario description based on text with "to be removed" non-alphabetical or non-numerical characters

Settings

• In later version we might consider setting(s) allows that user somehow to manage length of feature description

[DavidFeldhoff]

@martonsagi

• Hardcode the 30 characters limitation in the Feature description
• Enable to add a new feature and send the following values in the messageUpdate: State = New, Type = Feature, newValue = Feature description entered by the user.

I'll add a new file on my own and add it under the folder specified in the settings.

[lvanvugt]

@DavidFeldhoff, it seems to me that this Use Case: Adding Feature is far from ready.

When adding a new feature in Features pane, by creating a new text box and entering a name it:

• an extra control with same descriptions is appearing
• the codeunit created:
  • does have id 0 (would expects it to from id range in app.json
• is not formatted, cannot be formatted, and has a lot of unwanted commas
  codeunit 0 "New Feature"{, Subtype = Test;,, trigger OnRun(), begin, // [Feature] New Feature, end;,, [Test], local procedure NewTestProcedure(), // [Feature] New Feature, begin, // [Scenario #0001] New Test Procedure, end;,}

[DavidFeldhoff]

Hi Luc, I agree there were some issues. I fixed it on the backend-site, but the extra control with the same description has to be fixed by @martonsagi
Marton, can you have a look at it?
And regarding the object ID: I added a solution which is working for now, but I'd like to add a API to the extension of Andrzej (AZ AL Dev Tools). He has a more robust solution to get the next codeunit ID for his wizards. Or do you have something similar in place Marton in your AL Studio extension?

[DavidFeldhoff]

Maybe one more info: in the latest commit I pushed changes that worked in my easiest tests, but I haven't tested it yet enough to say it has a "ready" status ;)
But I still pushed the changes as Marton can step in now to fix the other bug.