👀 Extension Architecture / API

## Overview

Support for extensions is planned for a future release of CodeEdit. The extension system will provide similar capabilities to that of other editors.

## Contributing

If you wish to contribute to building the CodeEdit extension architecture, please see the tasks below and review the relevant parts of the [API documentation repository](https://github.com/CodeEditApp/documentation). This documentation should be used as the guide for development.

**PLEASE NOTE THE DOCUMENTATION IS STILL WORK IN PROGRESS. TASKS AND THEIR RELATED GITHUB ISSUES WILL BE UPDATED AS THE RELEVANT DOCUMENTATION IS COMPLETED.**

Each API feature functionality first needs to be built into CodeEdit so that it can be used internally by the application and then later exposed to extensions through the API.

## Tasks
- [ ] CodeEditApp/CodeEdit#180
- [ ] CodeEditApp/CodeEdit#183
- [x] CodeEditApp/CodeEdit#167
- [ ] CodeEditApp/CodeEditTextView#32
- [ ] CodeEditApp/CodeEdit#391
- [ ] CodeEditApp/CodeEdit#222
- [ ] CodeEditApp/CodeEdit#220
- [ ] CodeEditApp/CodeEditTextView#40
- [ ] CodeEditApp/CodeEdit#224
- [ ] CodeEditApp/CodeEdit#262
- [ ] CodeEditApp/CodeEdit#392
- [ ] Data Storage
- [ ] Display Notifications
- [ ] Themes
- [ ] Custom UI support with React Components
- [ ] Extension Debug Console
- [ ] CodeEditApp/CodeEdit#107

## References

- [Atom Extension API](https://flight-manual.atom.io/api/v1.57.0/)
- [VS Code Extension API](https://code.visualstudio.com/api)
- [VS Code Extension Examples](https://github.com/microsoft/vscode-extension-samples)
- [Raycast Extension API](https://developers.raycast.com)
- [Nova Extension API](https://docs.nova.app/)
- [Sketch Extension API](https://developer.sketch.com/reference/api/)