Open mitchcapper opened 2 years ago
We implemented save-to-gist in an earlier prototype but the feature did not make the public release.
This is something I am considering revisiting. One reason why we have not turned this back on is because we have had some feedback from users that gists are not ideal for managing libraries. I've been looking at more robust publishing and sharing techniques, but nothing concrete so far.
Happy to mark this is an enhancement request for tracking and feedback.
I think the world of community extensions, especially of small amounts of code, can be complex to get right.
There are some examples however of gists being used in similar fashions like home assistant for their blueprint system: https://www.home-assistant.io/docs/automation/using_blueprints/
In fact their solution that was only a couple hundred lines of code worked for GH repos, gists, and their forums. It wasn't a perfect solution as it doesn't currently allow syncing updates down. It also doesn't have this projects problem of needing to write code into libraries for many users.
Now home assistant doesn't allow syncing with gist updates currently but that is not really due to technical gist/github limitations.
There are some benefits to gists including
Not all of these things are likely important for this plugin, but many of them probably are useful. It also gives a quiet way of dealing with conflicts as the conflict version can be committed right into the tree prior to being overwritten.
Excel formulas are likely to be small amounts of code I think lends itself to requiring simple sharing and consumption, and short of dedicated solutions around AFE may make things more cumbersome. AFE clearly already strives for this by allowing quick copy and pasting of formulas, but copy and paste is rarely a great sharing solution.
Given the CORS restrictions out there a widely used platform like GH may give users some level of autonomy of library design without the complexities of supporting many different platforms.
An imperfect solution that works today can be greatly preferred to the perfect solution just over the ever moving horizon (not to mention you already have most [all?] the code to support it:). Just do what anyone who wants to abandon a possible child feature does and hide it under an experimental beta expert only flag.
The gist library support (or any library source including onedrive) would be great for more rapid connections between workbooks.
There seems to be much of the work done, and at least github token api seems like it wouldn't be too far from fully working (although the oauth code seems like it would be fine too just can't test that easily).
The ticket can at least track the feature if there isn't any additional information for now.
Currently using an external app for some synchronization of named formulas across files but would be great here.