Hi 1Password folks,
I'm not sure if I'm posting this in the right place - feel feel free to move it if desired.
This past week, I've spent a fair amount of time reworking the mrc-converter-suite to import 1PUX. And I made great progress, but I've hit what I feel is a major stumbling block.
Feel free to say, "Hey MrC, we don't want your stinkin' converter suite any longer" and I'll stop, and you can stop reading...
Hopefully you are still reading...
Trying to determine the cause of failed imports is very difficult (the log is woefully inadequate for this). I've had to work via trial and error. Yesterday, I achieved my first successful import. It took a while to discover that certain attributes are required, or the import will fail. An item's createdAt and updatedAt were the first two surprises. This requirement is new to 1PUX.
Today's major problem occurred as I try to import stock template sections / fields. When any of the field attributes guarded, multiline, dontGenerate or inputTraits (or any of its attributes keyboard, correction, capitalization) are missing, the import will fail. The requirement of such attributes is also new to 1PUX.
And this is a major problem. First, it means that I have to know all the values for those attributes for every field. That's not an impossible task, but is a problem if a) you change any of those attributes, b) I get any wrong, which will create issues for you and users - they can delete a field that would ordinarily be guarded, or a password generator doesn't appear when it should, the wrong keyboard is used, etc. (users will have no way to fix such issues).
Previously, the field's "id" was sufficient for a 1PIF import to match the proper field within a category's template. I think the same should be true for a 1PUX import wrt. not requiring the previously mentioned attributes. 1Password's template values for the "id" should be used to set default attribute values, so that they are not required to be in the 1PUX. But if these attributes are present in custom fields, they should be used. Likewise, the same for createdAt and updatedAt, which should both default to the time of import when absent.
I think all the fields in yellow below should be optional - use if present, default values assigned on import if missing:
Other attributes aren't yet clear to me, such as state, and I presume indexAtSource is the field's index order within a section.
The 1PUX document has a few issues. I'm happy to provide details if you're interested.
Finally, I've been hoping to be able to use the CLI instead of 1PIF / 1PUX for this type of conversion / import. But it seems still not ready for this; I'm hoping it will be someday.
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser:_ Not Provided