Fixing damageOptionsMap logic

This commit is contained in:
Max 2022-02-14 12:29:32 -05:00
parent b7cc2cae26
commit d1ecf4d7b9
3 changed files with 2 additions and 3 deletions

View file

@ -41,7 +41,7 @@ describe("damage-location-question.vue", () => {
damageLocationQuestion.methods.initializeComponent.call(wrapper.vm, cmsContent, damageOptions, "car-group");
//Assert
expect(wrapper.vm.answersToDisplay).toStrictEqual([ { Name: 'car-Windshield' }, { Name: 'car-SideDoor' }, {Name: "car-RearWindow"} ])
expect(wrapper.vm.answersToDisplay).toStrictEqual([ { Name: 'car-Windshield' }, { Name: 'car-SideDoor' } ])
});
});

View file

@ -36,7 +36,7 @@ export default ({
damageOptions: Object,
}
},
props: {
props: {
isMultiSelect: Boolean,
modelValue: Array,
isAvailable: Boolean,

View file

@ -71,7 +71,6 @@ export default {
vm.$refs.funnelFooter.initializeComponent(
resultMap.cmsContent.FunnelFooterWidget
);
console.log(resultMap.damageOptions)
});
},
data(){