(feat) O3-3113: Add disallowDecimals validator

[jabahum]

Requirements

• This PR has a title that briefly describes the work done including the ticket number. If there is a ticket, make sure your PR title includes a conventional commit label. See existing PR titles for inspiration.
• My work conforms to the OpenMRS 3.0 Styleguide and design documentation.
• My work includes tests or is validated by existing tests.

Summary

This PR implements a validator in the form engine that validates whether decimal values should be allowed in numeric obs fields. This resembles the Angular form engine's similarly named disallowDecimals validator.

The Carbon NumberInput doesn't provide any special handling for decimal values, so this validator can step in if you want to mandate that a field should not support decimals, for example. A scenario where you'd want to use this is when representing a numeric field that's backed by a concept that has allowDecimal set to false, such as Platelets below:

{
  "name": "Test Form 1",
  "description": "Test Form 1 Description",
  "version": "1",
  "published": true,
  "retired": false,
  "encounter": "Consultation",
  "pages": [
    {
      "label": "Page 1",
      "sections": [
        {
          "label": "Section 1",
          "isExpanded": "true",
          "questions": [
            {
              "label": "CD4 count :",
              "type": "obs",
              "id": "cd4count",
              "questionOptions": {
                "concept": "161011AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA",
                "rendering": "number",
                "disallowDecimals": "true"
              },
              "validators": []
            }
          ]
        }
      ]
    }
  ],
  "processor": "EncounterFormProcessor",
  "referencedForms": [],
  "encounterType": "67a71486-1a54-468f-ac3e-7091a9a79584"
}

Screenshots

Related Issue

Other

[denniskigen]

@jabahum I've updated the PR description with extra context. It'd be cool if you could add a sample schema that shows how to leverage this validator, as well as a short video of it in action.

[jabahum]

@jabahum I've updated the PR description with extra context. It'd be cool if you could add a sample schema that shows how to leverage this validator, as well as a short video of it in action.

This has been added @denniskigen

[CynthiaKamau]

Thanks @jabahum , please address the conflicts so that we can close this

[denniskigen]

@jabahum I've tried filling in the Laboratory Test Results form and I don't see the validation kick in when entering decimal values for the Platelets and MCV fields, which don't allow decimal values.

[denniskigen]

@jabahum is the Lab Test Results form now getting validated correctly?

[hadijahkyampeire]

@denniskigen your issue has been fixed, it was because the question was lacking min and max, so I have set a default since all the validation bases on the question having min and max

[denniskigen]

@hadijahkyampeire the validation should be able to work regardless of whether min and max values are set. The basic premise should be that you're rendering a numeric field that doesn't allow decimals, so you add this validator to ensure that decimal values get flagged when entered into the input, min and max values notwithstanding.

[hadijahkyampeire]

okay @denniskigen I can make it that way, I had got some information that we want to validate if the number is within the range of the min and max, and honestly it wasn't sounding correct to me as well. Thanks I will make that change.

[samuelmale]

Just a few comments

All issues addressed