[matteozanettii]

Proposed changes

This PR adds the configuration for the zscoreFS function to the functionSignatures.json file.

Details of changes

Mapped inputs: X, loc, scale, and dim.
Choices: Added dropdown autocomplete suggestions for the optional arguments loc ('median', 'mean') and scale ('mad', 'Qn', 'Sn', 'std', 'modmadp').
Mapped outputs: Z, mu, and sigma.
The JSON structure matches the logic of the existing functions in the file, allowing the editor to correctly display parameter suggestions and descriptions while typing.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

[BoschiGiacomo]

Hi @matteozanettii, thanks for your submission. There is only one problem with autocompletions that are shown twice, in the following comments you can find a quick fix and explanation.

As soon as it's fixed we can merge your work, thanks.

[matteozanettii]

Hi @BoschiGiacomo , thanks for the review! There are all the changes I made:

Resolved the issue of duplicated dropdown choices across all functions (including the existing getTickers, getYahoo, and getFundamentals) by merging the "char" and "string" types with their "choices" into a single, unified block.,

Then fixed the syntax errors in topPanelMode and bottomPanelMode by removing the unsupported textual descriptions from the "type" arrays and moving them into the "purpose" fields;
Replaced the deprecated "optional" keyword with "ordered" for the zscoreFS positional inputs and changed the generic "numeric" output types to "double" to successfully pass the validateFunctionSignaturesJSON check.

However, compared to what we discussed together, I preserved the original logic of this exact JSON file instead of the other fuctionsignatures files

there is the check from the validator:

[BoschiGiacomo]

Hi Matteo, thanks for looking into the other signatures of the file as well. There is a problem introduced by your latest changes: flattening the type arrays changes their meaning from OR to AND; I have detailed it in the comment below.

From the MathWorks documentation:

To match any of multiple classes or attributes, use a list of lists of JSON strings. For the inner lists, MATLAB uses a logical AND of the values.

The same page uses "type":[["char"],["string"]] for an argument that accepts either class.

Once this is fixed, we can merge. Thanks.

[matteozanettii]

Hi @BoschiGiacomo , thanks a lot for the explanation and for taking a detailed look at the whole file!
Also thank you for teaching me the AND/OR logic issue introduced by flattening the arrays; I hadn't known that. The brief of changes:
I restored the nested brackets ([[...], [...]]) to correctly maintain the OR logic between types.
To fix the original issue with duplicate dropdown suggestions, I isolated the choices into their own dedicated sub-array (e.g., ["choices={...}"]).
I also fixed the text in the purpose fields for topPanelMode and bottomPanelMode, reverting to the short descriptions to avoid cluttering the MATLAB suggestion popup. (I made sure this applies to the whole file). I also rechecked with the validator if everything was right and reported me 0 errors
Everything should be in order now. Feel free to take a look when you have a moment and let me know if we are good to merge! Thanks again for the help.

[BoschiGiacomo]

Looks good to me. Thank you for your contribution, @matteozanettii!

I pushed a small fix removing 'modmadp' from the scale choices, since it's a placeholder and not a valid value.