-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New upload json feature, fixes & optimizations #247
Conversation
Implement new upload JSON feature
Fix locale key
Add nodes
Add lodash package for key checks Fetch accounts and assets found in prompt operations in batches.
Optimize Bitshares prompts
Fix issue bitshares#255 Enable sorting balance table Increased height of the balance table Fixed menu icon rendering
Translate the contents of prompts Change prompt UX to card, instead of text rows. Increased size of prompt window.
Localization needs further work, it seems the machine translations translated the variables, resulting in missing fields when switching between languages. Edit: Resolved! |
Fix locales with broken variable script
Replacing get and chunk functions
UX improvements to the injected call popup prompt Move approve/reject buttons to below ui card in prompt preview Account for testnet batch size limits
Basic check on the format of the incoming request
Fix settingsRow error Additional error checking Remove "Scan QR" button until issue bitshares#256 is resolved Prevent qrTX disrupting the ipcRenderer popup creation process Translate the permission prompt
Remove button temporarily
Replacing qrcode-reader-vue3 for vue-qrcode-reader package now that it supports vue3, resolving bitshares#256
this has conflicts? |
It seems to only be the package lock file which is conflicting? The package file was updated, I tried deleting the lock file but appveyor hasn't resolved the conflict despite the file no longer existing. The package json file has been updated to use the new QR code package |
What do you think of the new operation viewer & paginator component? My only reservation with it is that in its current format that a 3rd party app could sneak in an operation and the user doesn't check it, if there's several thousand operations in the prompt. What do you think about separate paginating operation components for different operation types? That way all the transfers would be grouped together, and any non-transfers would be visible below the transfers for example? It might be a bit of a cluttered edge case to resolve |
Any user that executes thousands operations is probably a power user, and will not need special considerations and protection |
Implement new upload JSON feature to address #246
Introduced a fix for TUSC: #248
Introduces optimized account/asset lookup for all BTS operations: #249
Fix balances rendering properly: #255
Localizes the contents of BTS blockchain based injected operation prompts: #252
Resolves #256