CodeEditApp/CodeEdit

👀 Extension Architecture / API

Open

#76 opened on 2022年3月19日

GitHub で見る
 (9 comments) (4 reactions) (0 assignees)Swift (22,856 stars) (1,165 forks)batch import
PRIORITYclarification neededenhancementextensionshelp wanted

説明

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. 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
  • 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

コントリビューターガイド

技術スタック
swift
領域
desktopapideveloper experience
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
5
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
SwiftCodeEdit codebase familiarityExtension API design patterns
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
10
調査方針
Review the CodeEdit documentation repository at https://github.com/CodeEditApp/documentation to understand the planned API. Examine the linked substasks such as #180, #183, and #167 to identify which features are already implemented. Note that the documentation is a work in progress, so contacting maintainers for clarification on priorities may be necessary.