Users can create saved explores

Now that we have users, we should try implementing a feature that requires using user_id (because we don’t just want to have users for the sake of tracking…)

This is also a really important, quite basic feature for the app.

A user should be able to save an explore. When they save an explore, it appears in their saved explores page (see #233 )

Should create event for saved_explore_created: #236

https://www.sketch.com/s/5f6d7184-0fd0-4bde-925f-0f2d043f103b

[ZeRego]

do you imagine we’ll ever want to save queries and charts separately?

@owlas Each saved chart would still be linked to a saved query.

This sounds similar to Jira. When you want to build a chart/table in a Jira dashboard you need to select a saved query.

When fetching the saved query we could get all the linked saved charts. We could apply the first in the list and provide a dropdown in the UI for people to switch between all the saved charts.

We could leave the work for the multiple saved chart configs for a future ticket.

[TuringLovesDeathMetal]

@hamzahc1

Does a saved explore include things like: sorts on columns, chart settings OR just the queries?

Yes, it should be basically save the state that your explore is in the moment that you’ve saved it (so, I think this is same thing as our current share link functionality 🤔 )

Note: Also think about error handling, what do we do if underlying model changes on a saved explore?

I actually wouldn’t worry about this…(for now). I would say that > 90% of model changes will not change the overall ‘logic’ of the model. If anything, changes will fix broken logic, so it would be really hard to actually give error handling because we wouldn’t know if the changes were fixing or breaking changes. Also, if you change a model, you’ll tend to change values within a model, and not the overall model structure (e.g. I might change the way I calculate average time spent in the app on my users table, but it’s reeeeallllyyy unlikely that I’d change the fact that the table is one row per user_id)

I guess the one type of error handling we could do is telling the user that the data has changed since the Explore was saved? But I feel like this might do more harm than good…(e.g. how would you then go and figure out what has changed? What happens if multiple columns have changed multiple times since the Explore was saved? etc.)