Perry Mitchell

Yeah, it's probably because the card number is saved as "password" in the guts of the vault.. So it should probably be changed to avoid password and the CVV set...

Sorry for replying so late @xWayfarer - This is definitely something we'd like to look into quite soon. It would be beneficial to keep it as simple as possible in...

@hd719 You certainly can! I've updated the description to be more in line with what we'd want. Please let me know if it still interests you - this one is...

The trouble with this issue is that fields are stored on Entries as `key: value`, and don't contain any associated attributes. Every entry has a hidden `attributes` collection, which is...

Ok, so I'd go about this process in the following manner, if I were tackling it: 1. Add a constant in `Entry.js` to hold the **prefix** for field orders, as...

So, as an example, let's say we have the following setup: | Property | Order | Attribute name (eg.) | |-----------|-------|----------------------| | username | 0 | `BC_ENTRY_FIELD_ORDER:username` | | password...

Also good to note that the `deleteProperty` method should be modified to also delete the order attribute, if it exists. I'm not sure that `setProperty` _needs_ to set the order,...

@ldexterldesign Yes API.md in the root is generated from JSDoc comments..

Hmm. We use fuzzy search to handle matching in a quick manner, but it probably needs some tuning. It's perhaps a bit too sensitive.

Hmm.. I quite like the idea. Not sure how it'd work in our current interfaces. Definitely happy to explore the idea however. I wonder how searching might work - right...