Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: do not use ancestor parse when the model defines a new dataset #7498

Merged
merged 1 commit into from
Aug 17, 2021
Merged

fix: do not use ancestor parse when the model defines a new dataset #7498

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 4 additions & 1 deletion src/compile/data/parse.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -300,9 +300,12 @@ export function parseData(model: Model): DataComponent {
let head = parseRoot(model, model.component.data.sources);

const {outputNodes, outputNodeRefCounts} = model.component.data;
const ancestorParse = model.parent ? model.parent.component.data.ancestorParse.clone() : new AncestorParse();
const data = model.data;

const newData = data && (isGenerator(data) || isUrlData(data) || isInlineData(data));
const ancestorParse =
!newData && model.parent ? model.parent.component.data.ancestorParse.clone() : new AncestorParse();

if (isGenerator(data)) {
// insert generator transform
if (isSequenceGenerator(data)) {
Expand Down