Pavel Kasila
Pavel Kasila
@jasonplatts, I think that it's related to #76
As @lukepistrol said, we implement API for extensions to provide targets, tests and so on. So, NodeJS extension reads `package.json` and creates `npm start` target and anything else using Extension...
I would prefer using Swift for extensions, but having JavaScript API would be nice to have also, considering that the app may be ported to iPadOS later. So, I think...
So, in my opinion, Swift Extension Architecture can be implemented the way described below. ## Swift API So, let's say we have a `CodeEditExtensionAPI` package that declares protocols to work...
> Are we able to automate and simplify this process from the extension developers perspective through CodeEdit? Maybe a "Package and Submit Extension…" menu item? I think we can determine...
@viktorstrate Looks good! Actually I forgot about `Bundle`s when I was writing. I think they can fit all of our needs
> @pkasila Does this fall in line with what you were working on? Any thoughts on this approach? I was working on a different approach (but I was working on...
I'm working on the PoC for Extension Store API, so I hope I'll be able to show some demos of how it can be implemented by Monday-Tuesday