Add support for gitea/forgejo backed

[nakibrayan3]

this is the only thing holding me back from switching to svelita-cms

[kyoshino]

As mentioned in the README, we have no plans to support Gitea/Forgejo at this time for performance reasons. Basically, there is no way to get multiple files at once, requiring 100 requests to fetch 100 files, which is a non-starter. We will reconsider it if/when their API improves in the future.

[oliverpool]

For anyone interested in implementing it on the Forgejo/Gitea side

The forge would need to expose an API allowing efficient implementation of the BackendService api:

sveltia-cms/src/lib/typedefs.js

Lines 69 to 93 in a2b3773

	/**
	* Backend service.
	* @typedef {object} BackendService
	* @property {string} name - Service name, e.g. `github`.
	* @property {string} label - Service label, e.g. `GitHub`.
	* @property {RepositoryInfo} [repository] - Basic repository info. Git and local backends only.
	* @property {string} [statusDashboardURL] - URL of status dashboard page of the service. Git
	* backends only.
	* @property {() => Promise<BackendServiceStatus>} [checkStatus] - Function to check the backend
	* service’s status. Git backends only.
	* @property {() => RepositoryInfo} [getRepositoryInfo] - Function to get the configured
	* repository’s basic information. Git backends only.
	* @property {() => void} init - Function to initialize the backend.
	* @property {(options: SignInOptions) => Promise<User | void>} signIn - Function to sign in.
	* @property {() => Promise<void>} signOut - Function to sign out.
	* @property {() => Promise<void>} fetchFiles - Function to fetch files.
	* @property {(asset: Asset) => Promise<Blob>} [fetchBlob] - Function to fetch an asset as a Blob.
	* Git backends only.
	* @property {(changes: FileChange[], options: CommitChangesOptions) =>
	* Promise<string | (?File)[] | void>} commitChanges - Function to save file changes, including
	* additions and deletions, and return the commit URL (Git backends only) or created/updated files
	* (local backend only).
	* @property {() => Promise<Response>} [triggerDeployment] - Function to manually trigger a new
	* deployment on any connected CI/CD provider. GitHub only.
	*/

I think the main challenge would be fetchFiles, which usually calls the common fetchAndParseFiles function, which call the forge-specific fetchFileList function, which must return the whole tree of files (path + sha):

sveltia-cms/src/lib/services/backends/gitlab.js

Lines 342 to 348 in a2b3773

	/**
	* Fetch the repository’s complete file list, and return it in the canonical format.
	* @returns {Promise<BaseFileListItem[]>} File list.
	* @see https://docs.gitlab.com/ee/api/graphql/reference/index.html#repositorytree
	* @see https://stackoverflow.com/questions/18952935/how-to-get-subfolders-and-files-using-gitlab-api
	*/
	const fetchFileList = async () => {

[nakibrayan3]

I wish I had the experience to implement something like this.

[kyoshino]

Well, once Gitea/Forgejo is updated to provide a better API, I’m happy to implement it. I have seen discussions on the Forgejo forum, and oh, @oliverpool has left some comments there 🙂

[kyoshino]

Aside from Forgejo support, Sveltia CMS doesn’t yet support RTL, which is probably what @nakibrayan3 needs. Netlify/Decap CMS has an issue for this since 2019, and it’s also on my todo list, as Sveltia CMS has to offer first-class i18n support 😆 (and my native Japanese was also kinda RTL at some point in history.)

• Support RTL in the Preview pane decaporg/decap-cms#2524

[nakibrayan3]

Thanks to every one here helping :)

[kyoshino]

I’ll keep this open for future possibilities. #31 has an interesting idea, btw.