fix: Add error handling in VariableCreateUpdateForm and wrap text in ItemValue

[fit2bot]

fix: Add error handling in VariableCreateUpdateForm and wrap text in ItemValue

[fit2cloudrd]

The provided code contains slight syntax errors which can cause issues during evaluation. Here are some corrections:

• At @import there should not be a space before the double quote symbol.
• The function name inside brackets {} must start from an uppercase letter.

Here's the corrected version of the code according to these guidelines:

export default {
   rules: [
      {
        validator: (rule, value, callback) => {                
          var arrayLines = value.split("\n");
          // Regular Expression pattern will match line with exactly two ":" separated fields
               const regex = /^\s*:?\S+: ?(\w*)$/;
              for(let i=0; i < arrayLines.length;i++) 
              {
                 let val =  arrayLines[i].replace(/\n/g,'');
                let regMatch = arrayLines[i].match(regex);    
                if(!regMatch)return;
            if(arrayLines[i] != ""){
               return false;
             

This is where the first error resides; it suggests that each line needs to start with whitespace followed by either a colon on every field other than the second one. For example, "colon\ssomething". Also, ensure proper indentation and formatting within curly braces.

[fit2cloudrd]

There's no error found with this line of code.

The difference between this modified version and the original could be:

• The displayValue prop is an optional property which can contain one or more values separated using commas.

And here's some general code style tips to improve readability:

1. It often helps if you indent blocks that define rules rather than separate things with whitespace.

       export default {
        ...
         // Define these variables outside their usage 
          var displayValue = '';
           if (value != null) {  
               displayValue += value;
            } else  {
               ...
   

2. Ensure that your props should have type annotation:
    ```
export default ({
     ...
}) => ({ ... }

3. You need proper handling of edge cases where null may exist.

   if(value === null && hasNonNumericValue){
       // handle non numeric value when `hasNonNumericValue` == true
   }

4. Consider wrapping elements such as <span>'s to prevent them from being interpreted as inline content, which makes them behave like block-level tags in JSX.

   return(
     <span>
        ...
     </span>
   )
   
   

5. Also ensure that you're checking all properties on the object before doing anything with it:

Object.entries(propToCheck).forEach(([key, val]) =>{
if (!val || typeof val !== 'object'){
    // Do something different...
}
})

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud