Closed aurimasv closed 10 years ago
Oh, one thing. Unfortunately, the first updates using the new Scaffold version will create a large amount of field jumping, but hopefully that should be the end of it!
haven't looked at the code, but indeed very happy with the change as such.
On Fri, Jun 27, 2014 at 1:51 AM, Aurimas Vinckevicius < notifications@github.com> wrote:
Oh, one thing. Unfortunately, the first updates using the new Scaffold version will create a large amount of field jumping, but hopefully that should be the end of it!
— Reply to this email directly or view it on GitHub https://github.com/zotero/scaffold/pull/16#issuecomment-47316921.
Sebastian Karcher, PhD Department of Political Science Northwestern University
Looks good to me.
I tested this a bit and it seems to work ok. We'll see if we get any bugs as we go.
This accomplishes two things:
When running
doWeb
ordoImport
in Scaffold, it will display which item fields will be removed/renamed when the item is actually imported into Zotero. The display is similar to what we see when running tests.When saving tests, Scaffold will now save the item fields in a deterministic (sorted) way. This means that we should no longer see fields randomly moving around in diffs when updating tests. It will also sort tags, which sometimes tend to jump around. Most of the fields are sorted alphabetically, but I decided that itemType, title, creators, and date (the most important metadata) should always be at the top. I also moved stuff that's rarely used/takes up a lot of space, to the bottom of the list (i.e. tags, seeAlso, attachments, notes).
Thoughts? (I think @adam3smith should like these changes. I'm certainly enjoying them)
Here's an example: Before
After