gristlabs_grist-core

Commit Graph

Author	SHA1	Message	Date
Alex Hall	d1a848b44a	(core) Parse string cell values in Doc API and Imports Summary: - Adds a function `parseUserAction` for parsing strings in UserActions to `ValueParser.ts` - Adds a boolean option `parseStrings` to use `parseUserAction` in `ActiveDoc.applyUserActions`, off by default. - Uses `parseStrings` by default in DocApi (set `?noparse=true` in a request to disable) when adding/updating records through the `/data` or `/records` endpoints or in general with the `/apply` endpoint. - Uses `parseStrings` for various actions in `ActiveDocImport`. Since most types are parsed in Python before these actions are constructed, this only affects references, which still look like errors in the import preview. Importing references can also easily still run into more complicated problems discussed in https://grist.slack.com/archives/C0234CPPXPA/p1639514844028200 Test Plan: - Added tests to DocApi to compare behaviour with and without string parsing. - Added a new browser test, fixture doc, and fixture CSV to test importing a file containing references. Reviewers: georgegevoian Reviewed By: georgegevoian Differential Revision: https://phab.getgrist.com/D3183	3 years ago
Jarosław Sadziński	1ae586cf42	(core) Adding Skip options when importing multiple tables. Summary: Adding new destination "Skip" for multiple table imports. Selecting this destination skips the import and makes the preview grayed out. Test Plan: New Tests Reviewers: georgegevoian Reviewed By: georgegevoian Differential Revision: https://phab.getgrist.com/D3181	3 years ago
George Gevoian	c6aa9b65d4	(core) Fix bug preventing importing of nested json files Summary: BulkAddRecord when finishing imports of nested JSON was throwing an error due to unchecked access of referencing tables. This adds a guard to prepare_new_values to handle such cases. Imports happened to cause this to occur because the order that imported tables are created/populated isn't aware of references between tables, so it's possible for a reference column to exist (momentarily) without a valid reference to another table. These references are currently fixed after all imported tables are created/populated. Test Plan: Browser test. Reviewers: dsagal Reviewed By: dsagal Subscribers: dsagal Differential Revision: https://phab.getgrist.com/D3144	3 years ago
George Gevoian	08b1286f4f	(core) Add column matching to Importer Summary: The Importer dialog is now maximized, showing additional column matching options and information on the left, with the preview table shown on the right. Columns can be mapped via a select menu listing all source columns, or by clicking a formula field next to the menu and directly editing the transform formula. Test Plan: Browser tests. Reviewers: jarek Reviewed By: jarek Differential Revision: https://phab.getgrist.com/D3096	3 years ago
George Gevoian	62db263d1f	(core) Add diff preview to Importer Summary: Updates the preview table in Importer to show a diff of changes when importing into an existing table and updating existing records. Test Plan: Browser tests. Reviewers: paulfitz Reviewed By: paulfitz Differential Revision: https://phab.getgrist.com/D3060	3 years ago
George Gevoian	e1780e4f58	(core) Migrate import code from data engine to Node Summary: Finishing imports now occurs in Node instead of the data engine, which makes it possible to import into on-demand tables. Merging code was also refactored and now uses a SQL query to diff source and destination tables in order to determine what to update or add. Also fixes a bug where incremental imports involving Excel files with multiple sheets would fail due to the UI not serializing merge options correctly. Test Plan: Browser tests. Reviewers: jarek Reviewed By: jarek Differential Revision: https://phab.getgrist.com/D3046	3 years ago
George Gevoian	8a7edb6257	(core) Enable incremental imports Summary: The import dialog now has an option to 'Update existing records', which when checked will allow for selection of 1 or more fields to match source and destination tables on. If all fields match, then the matched record in the destination table will be merged with the incoming record from the source table. This means the incoming values will replace the destination table values, unless the incoming values are blank. Additional merge strategies are implemented in the data engine, but the import dialog only uses one of the strategies currently. The others can be exposed in the UI in the future, and tweak the behavior of how source and destination values should be merged in different contexts, such as when blank values exist. Test Plan: Python and browser tests. Reviewers: paulfitz Reviewed By: paulfitz Subscribers: alexmojaki Differential Revision: https://phab.getgrist.com/D3020	3 years ago
Paul Fitzpatrick	5ef889addd	(core) move home server into core Summary: This moves enough server material into core to run a home server. The data engine is not yet incorporated (though in manual testing it works when ported). Test Plan: existing tests pass Reviewers: dsagal Reviewed By: dsagal Differential Revision: https://phab.getgrist.com/D2552	4 years ago

8 Commits (cebd7b2d74c9dcf9624f01781f876333bb546590)