CodeEditApp / CodeEditApp/CodeEdit
🧹 Refactor CodeEditCli
- Lenguaje dominante
- Swift
- Estrellas
- 23k
- Forks
- 1.2k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
## Current Situation
~~At the moment~~ [Previously] the `CodeEditCli` is just a standalone SPM package in our main repo:
> https://github.com/CodeEditApp/CodeEdit/tree/main/CodeEditTests
**Edit:** Now it is in the CodeEditCLI repo.
The built binary is then included as a resource in our main workspace:

## The Problem
The problem with this approach apart from having a binary in our sources, which technically isn't needed, is that it prevents our app from notarizing.
## Proposed Solution
~~I suggest moving the `CodeEditCli` package to a new repo (like `CodeEditTextView`) and then attach the binary to a tagged release as an artifact.~~
I may also suggest renaming the artifact to `codeedit-cli` in order to make clear what the binary really is. An alias `codeedit` can always be created by the user if needed.
This would mean the main app needs to download the latest artifact and move it to the according location in `GeneralPreferencesView.swift:215`. The location should be `/usr/local/bin/codeedit`.
Additionally we could also add it to `homebrew` as a formula `codeedit-cli`.
Please let me know what you think about that approach and let's discuss what could be improved further in this regard. I then will create the repo in the organization.
Guía de contribución
Evaluación
Este issue todavía no se ha evaluado.