Closed twelch closed 1 year ago
Yes! Slugified names would be much better. This single export endpoint serves 3 use-cases which may need to be split:
Currently the client dynamically creates urls to reference sketches, and if we're using slugified names I'd want to centralize that logic and expose an exportUrl property in the GraphQL Schema so that there's no chance of mismatched id generation. Map visualization probably needs a different endpoint, since mapbox-gl-style can't reference the userAttributes property.
I may be able to use the download/attachment header to let the browser rename 12.geojson.json => my-sketch.geojson.json
and avoid a lot of the mess with complex url referencing... but I thought I was already doing that.
As a degenerate who piles all my files all into ~/Downloads and uses search to find things, I still like the geojson.json
part of the filename and think I will keep that. Just .geojson
isn't recognized by QGIS by default and it's easy to confuse what the files are without the extension.
When exporting a sketch to geojson:
.geojson.json
. Just.json
seems as with legacy seems fine with me.