Skip to content

Make frame with nulls clear items & array containers #1118

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

Merged
merged 11 commits into from
Nov 11, 2016
Merged

Make frame with nulls clear items & array containers #1118

Changes from 1 commit
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
69bffe1
test: add cases for Lib.expandObjectPaths w/ array containers
etpinard Nov 7, 2016
4c49755
make clean data work for non-plain-object annotation / shape items
etpinard Nov 9, 2016
d21d782
add general array container defaults handler
etpinard Nov 9, 2016
138ac35
DRY layout array container defaults using handleArrayContainerDefaults
etpinard Nov 9, 2016
d0953a0
test: add cases for array container defaults
etpinard Nov 9, 2016
174b640
make sure array containers set to null in frames are honored
etpinard Nov 9, 2016
36859f1
make sure items inside array container set to null are honored in frames
etpinard Nov 9, 2016
66f8bb7
test: add cases for extendObjectWithContainers
etpinard Nov 9, 2016
8ed1957
Merge branch 'master' into frame-extend-with-nulls
etpinard Nov 10, 2016
9de2f77
make annotation/shapes cleanLayout blocks more robust
etpinard Nov 10, 2016
5de6ff0
split container opts from item opts in handleArrayContainerDefaults
etpinard Nov 10, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
67 changes: 67 additions & 0 deletions test/jasmine/tests/plots_test.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -427,4 +427,71 @@ describe('Test Plots', function() {
expect(gd._transitioning).toBeUndefined();
});
});

describe('extendObjectWithContainers', function() {

function assert(dest, src, expected) {
Plots.extendObjectWithContainers(dest, src, ['container']);
expect(dest).toEqual(expected);
}

it('extend each container items', function() {
var dest = {
container: [
{ text: '1', x: 1, y: 1 },
{ text: '2', x: 2, y: 2 }
]
};

var src = {
container: [
{ text: '1-new' },
{ text: '2-new' }
]
};

var expected = {
container: [
{ text: '1-new', x: 1, y: 1 },
{ text: '2-new', x: 2, y: 2 }
]
};

assert(dest, src, expected);
});

it('clears container items when applying null src items', function() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This also looks like what I'd expect. Am I correct in understanding that [undefined, undefined] would skip applying any changes?

var dest = {
container: [
{ text: '1', x: 1, y: 1 },
{ text: '2', x: 2, y: 2 }
]
};

var src = {
container: [null, null]
};

var expected = {
container: [null, null]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

N.B. I changed the behavior here as discussed in #1118 (comment) - see 36859f1

In brief, frames with array containers set to null extend the state with null. It is now up to the subsequent supplyDefaults calls to coerced those null items into {}, as in regular Plotly.plot calls.

};

assert(dest, src, expected);
});

it('clears container applying null src', function() {
var dest = {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Ditto on behavior of undefined?

container: [
{ text: '1', x: 1, y: 1 },
{ text: '2', x: 2, y: 2 }
]
};

var src = { container: null };

var expected = { container: null };

assert(dest, src, expected);
});
});
});