parametersResolution: Handle ENUM properties

[thim81]

Linked to #817

[thim81]

@VShingala The PR is ready for your review.

The issue originated in the resolveSchema function, which is solved in the PR.
There are a number of tests added.

There is an unexpected side-effect in the Validation tests, which I can't figure out what would be the expected result, perhaps you can assist?

ValidateV2.test.js (Line 577)

 expect(_.includes(['Bulldog', 'Retriever', 'Timberwolf', 'Grizzly', 'Husky'],
          propertyMismatchMap.BODY.suggestedFix.suggestedValue.breeds[2])).to.eql(true);

In the past this returned a random ENUM value with parametersResolution: schema, while now it will return <string>.

I find it strange the "ValidateV2" fails, since I've build it to only execute the conversion when the operation is "CONVERSION".

[thim81]

@VShingala Picking this PR up again.

Can you have a look at my previous question ☝️ , and what would be the expected behaviour?

1. Return schema type ()?
2. Return one of the ENUM values?

[VShingala]

@thim81 Although we've only updated conversion logic, validation logic/tests works hands in hands with it. i.e. tests failing are due to converted collection not getting validated after this change.

In validation workflow, we suggest changes based on schema. Till now these suggestions were of actual enums but from now they'll be "<string>" because the utility to suggest changes based on schema is used from functions present in schemaUtilsV2.

[thim81]

hi @VShingala

So if I understand properly, I can update the validation test to check for the <string>?

For me it is not really clear, how to fix the validation tests, without impacting the expected behaviour.