Co-authored-by: 19thyneb <thyne.boonmark@gmail.com>
Co-authored-by: Doris Lee <dorisjunglinlee@gmail.com>
Co-authored-by: NiStannum <52202164+NiStannum@users.noreply.github.com>

…org#336)

Co-authored-by: Caitlyn Chen <caitlynachen@berkeley.edu>
Co-authored-by: Doris Lee <dorisjunglinlee@gmail.com>

* added notebook gallery
* update README
* removed scatterplot message in SQLExecutor
* fixed typo in SQL documentation

…te (lux-org#297)

The LuxTracer can be used to keep track of executed code. It is currently being used in the executors to track which lines of code were used to generate individual charts' data.

This executor uses SQL query templates from a specified query file. Rather than having hard coded queries written in the executor itself, this executor leaves the query writing to users.

Currently works with Postgresql.

Added the _trace_code and _query parameters to Lux Vis objects. The _trace_code parameter will store the code used to execute the Vis data, and the _query parameter will store the SQL query used to first aggregate the data for the Vis in the SQLExecutor case.

Lux now only traces the code when a user calls the to_code() function of a Vis object. It does so by starting the tracer and re-executing the Vis object.
Cleaned up handling of for loops in the tracing processor.

Vis objects' _source parameter is now set within the execution function.

Updated the compare_vis() function to use .equals to compare the source dataframes.

Fixed bug where found_variable could be an empty list and was not set to "df"

Added functionality with scatter and bar charts. The query template file for compatibility with MYSQL is also included

Updated to work with the MySQL case, need to change how the executor uses quotations around different Database queries.

Updated the MySQL query template

Needed to update Executor files' code format to remove wrapped lines of code.

Fixed code formatting for the Pandas executor visualizations.

Changed the line formatting to fit the Lux Tracing use case

Removed unnecessary commented lines

…utor

Added in variable names to the templates to make it clearer what the inputs need to be

When a SQL connection is made to the Lux config, now defaults to using the Postgres SQLExecutor rather than the GeneralDatabaseExecutor