Within the code snippet below, we can see that in the
compPropsIsBtnDigitizePolygonDisableddigitizePolygonInteractions variable is initialized. If it is not initialized, an error will be triggered.
During execution, when the
compPropsIsBtnDigitizePolygonDisableddigitizePolygonInteractions has not yet been initialized. This causes the function to behave eagerly instead of lazily, resulting in the error being consistently thrown due to the uninitialized state of digitizePolygonInteractions.
I have a couple of queries regarding this issue:
- Is there a way to make
lazy rather than eager?compPropsIsBtnDigitizePolygonDisabled - How can I display the value of
digitizePolygonInteractionswithin the error message?
Code Example:
computed: {
compPropsIsBtnDigitizePolygonDisabled() {
if (digitizePolygonInteractions) {
if (isBtnDigitizePolygonClicked.value == true) {
digitizePolygonInteractions.remove();
return values.CONST_STRING_DIGITIZE;
} else {
digitizePolygonInteractions.add();
return values.CONST_STRING_STOP_DIGITIZE;
}
} else {
throw new Error('WTF.digitizePolygonInteractions is:', digitizePolygonInteractions)
}
},
}