Closed sg-s closed 1 month ago
a typical user flow is
right now, to do so, we have to worry about API calls where we have to laboriously pass database ID, column IDs, etc.
the dataframe warns user that there are unsynced changes
to_deeporigin
we create a new class that subclasses a pandas dataframe, and write special methods to talk to the data hub
problem description
a typical user flow is
right now, to do so, we have to worry about API calls where we have to laboriously pass database ID, column IDs, etc.
proposed solution -- ux
1. user creates a df using pandas-like syntax
2. user modifies some data
the dataframe warns user that there are unsynced changes
3. user uses pandas-like
to_deeporigin
df method to write changes back to DO4. user views df again
5. user turns on auto_sync to live dangerously
6. user makes some changes
technical implementation
we create a new class that subclasses a pandas dataframe, and write special methods to talk to the data hub
changes
support for intelligently creating new columnswon't do this PRchanges post review
to_deeporigin
will print a message to console