Method implementation question - gas-fakes

[brucemcpherson]

This is more of a question than an issue.

I've been looking at this repo and I see an overlap with https://github.com/brucemcpherson/gas-fakes which esentially mimics apps script services as workspace api calls. There's currently about 1600 methods implemented in gas-fakes - with an ambition to do about 6000. identified so far. I'm not sure how if we will handle html service and other UI services at this point, but we'll see.

Obviously this extension is about allowing ag to interact with selected services via api calls (as opposed to allowing apps script code to be run locally). The gas-fakes approach works by telling AG to generate appscript code and run it locally to interact with workspace. What's your plan for this extension - are you aiming to cover all methods/all services, or just a subset of the common ones?

[allenhutchison]

The extension started off as a 20% exploration to meet my own needs, and I've built up functionality based on feedback since. I don't think it will every cover all of the functions in workspace (and some of them don't really make sense in the context of Gemini CLI). My loosely held plan is to continue to develop the features of the extension organically as feedback comes in and as my needs and time allow.