Esefah meng history strip

[NanaKwame]

This PR includes:

• changes for showing the history at the bottom of the page
• DnD of the history items.
• Being able to drag history items to x, y, fill or size on the bubble cursor and see scale updates
• Being able to drag history items to the main chart but not on the bubble cursor to see aesthetic updates to marks: "size", "shape", "fill", "fillOpacity", "stroke", "strokeWidth"

TODOs amongst bigger todos:

• fix any issues that might come up with changes to exporter.ts and cleanSpecForPreview in demonstrations.ts
• figure out if I need to use History.ts
• other mark types aren't working perfectly. currently symbols work the best

[lgtm-com]

This pull request introduces 4 alerts when merging fdf2c63 into f805c6d - view on LGTM.com

new alerts:

• 4 for Unused variable, import, function or class

[jonathanzong]

nice work! i've left comments that i hope are helpful. since it's a working branch, i'll leave it up to you what level of detail you want to address them to before merging

[NanaKwame]

nice work! i've left comments that i hope are helpful. since it's a working branch, i'll leave it up to you what level of detail you want to address them to before merging

I have pushed changes to address your comments. Please send any feedback especially for cleanHistorySpec in HistortyList.tsx. Not sure if that is the right/ok way to go about removing interactions from the history previews.

[lgtm-com]

This pull request introduces 11 alerts when merging 82b2fa4 into f805c6d - view on LGTM.com

new alerts:

• 11 for Unused variable, import, function or class

[lgtm-com]

This pull request introduces 11 alerts when merging ba9b9fc into f805c6d - view on LGTM.com

new alerts:

• 11 for Unused variable, import, function or class

[lgtm-com]

This pull request introduces 1 alert and fixes 1 when merging 8515e2e into f805c6d - view on LGTM.com

new alerts:

• 1 for Unused variable, import, function or class

fixed alerts:

• 1 for Unused variable, import, function or class

[jonathanzong]

now that i think about it, these should use visState too. if we pass in an older visState to the exporter, we expect it to get the scale info for that state. using the store state will use the current scale info instead, which could cause problems.

this means that the getScaleInfoForGroup and getFieldsOfGroup functions should probably be edited to use visState as well, and all uses of those functions updated accordingly. could you add one more commit with that change?

[jonathanzong]

great work implementing the earlier feedback! your approach in cleanHistorySpec looks right to me. left one comment for one last refactoring task then you're good to go