Repository navigation
Conversation
Once a file is loaded, the source card lists every input with a remove button, and offers Add files, add-by-URL and dropping onto the card. Two or more inputs are combined into one output; each change re-inspects the combination, and a file that cannot join is not added, with the reason shown under the source step. Every input is registered in a directory of its own, so adding never overwrites. Errors name the user's files rather than virtual-FS paths. Merging no longer refuses types the reader merely inferred differently between tiles (it infers from a sample of lines): numbers take the widest type, and text whose every value casts to the other input's type takes that type; a column empty in one input takes the other's. Values of a different kind are still refused.
Column types come from DESCRIBE, and a nested type's field names come from the file being read, so pasting a resolved type into CAST(... AS <type>) / ALTER ... SET DATA TYPE let a crafted input inject SQL. A merge now resolves a type difference only to a fixed set of scalar types (numbers, VARCHAR, BOOLEAN, DATE, TIME, TIMESTAMP[ TZ]) and refuses anything else as a schema conflict, so no type string from a file reaches SQL.
npm's 'latest' lags a fresh publish (a first publish briefly showed 0.0.0-stage), so the run after v0.0.1 tried to release 0.0.0-stage and failed. The version now comes from the newest vX.Y.Z tag, which Publish to npm pushes, and the release waits up to two minutes for npm to serve that exact version of both packages.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
releaseworkflow: releases the newest vX.Y.Z tag once npm serves it (the v0.0.1 run failed on npm's transient 0.0.0-stage)