web-version: Import/Export data

[huehnerlady]

Is your feature request related to a problem? Please describe.
I love the feature that you can try altair out in the web browser, so you get an even easier start to it. What I find dangerous though, is that you start trying it, then you love it and want to install the programme.... but then you have the problem, that you cannot export the data to move to the installed version, so you have to start from scratch again. The other thing is, that you cannot import data to try, you can import collections, but sometimes this is not enough (see #1690) with importing data you could also import the environment variables.

Describe the solution you'd like
I would like to get the import/export data functionality you have in the rich client, so people can get an EVEN EASIER start :)

[imolorhe]

Thanks for reporting this! I'd look into it as soon as I can. Considering the logic of importing and exporting is within the app logic itself, this should just be a matter of introducing the import/export actions within the app UI itself and wiring it up to the same logic, which should be pretty straightforward.

If anyone is feeling adventurous, I can help with reviewing a PR!

[AlexandruValeanu]

I can give this a go.

[imolorhe]

Go for it!

[huehnerlady]

Hi, I saw that there is a merged pull request, that looks promising :)

Any idea when this feature will be available on https://altair-gql.sirmuel.design/ ?

[huehnerlady]

@imolorhe any idea when this will be available on https://altair-gql.sirmuel.design/ ?

[imolorhe]

@huehnerlady I don't have a timeline. Currently that is only deployed when Staging gets merged to master, but that only happens now when ready for a release. I intend to deprecate the use of a staging branch and maintain only the master branch, which would also mean that https://altair-gql.sirmuel.design/ would always contain the latest changes even before release. For now however, that is not the case.

If you'd like to help with that process, searching for staging in the code base would give a good idea what needs to be updated in order to deprecate the staging branch.