Implement work-around/fix for incorrect render of manually added HOTP tokens

hicallmeal · web-flow · commit 41acb99c82e4 · 2024-07-02T03:55:37.000+10:00
The parsed `&lt;option&gt;` returns the OTP.type in string value, instead of the required integer type. Later in execution, the code can't handle the string in comparisons, etc. 

This just parseInts the string so that it's correctly handled.
diff --git a/src/components/Popup/AddAccountPage.vue b/src/components/Popup/AddAccountPage.vue
@@ -103,7 +103,7 @@ export default Vue.extend({
       ) {
         type = OTPType.hhex;
       } else {
-        type = this.newAccount.type;
+        type = parseInt(this.newAccount.type);
       }
 
       if (type === OTPType.hhex || type === OTPType.hotp) {

Original file line number	Diff line number	Diff line change
`@@ -103,7 +103,7 @@ export default Vue.extend({`
`103`	`103`	`) {`
`104`	`104`	`type = OTPType.hhex;`
`105`	`105`	`} else {`
`106`		`- type = this.newAccount.type;`
	`106`	`+ type = parseInt(this.newAccount.type);`
`107`	`107`	`}`
`108`	`108`
`109`	`109`	`if (type === OTPType.hhex \|\| type === OTPType.hotp) {`