Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
MrC
3 years agoSuper Contributor
1PUX - need some help
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-suit...
Former Member
3 years agoHi, again, MrC.
I'll happily help you with these.
For a little bit of context, especially with respect to error messages on missing fields, we're using a standard JSON parser for Rust. We declare the data structure that the parser should read into, and then the parser fails the first time it encounters a place where the available data doesn't match the structure itself. So on that front, we're going to be stuck with the very old style of "try, fix the first error found, try again".
But, the error messages we emit are, actually, very unhelpful. I'll see about improving them some, at least to the point of saying which field is missing. That feels insufficient, though, so I'll talk to our security folks to work out a plan for providing more information.
I'll research all of the other fields. I agree that some can be optional. The others are potentially optional, but I need to check for any extra issues that I may not be aware of.
What feedback would you like to provide with respect to the documentation? I'm too close to the system to understand the drawbacks of our current documentation, so I am definitely interested to know and to make things better.
Since I lead the Import project only a few weeks ago, I've let our CS team that I can be your point person for future technical issues here, too. I will often take a few days to respond as I have a lot of responsibilities, but I definitely want to help you with your work.