support Gitlab, Bitbucket, etc. in fink

[samuelstroschein]

Problem

The inlang editor only works with GitHub as a host.

Proposal

Make the inlang editor work with any git host.

Additional information

Support for multiple git hosts requires an abstraction layer over the numerous different APIs.

Ideally, lix has built-in functionality to abstract git hosts. For example, lix could export a function like createPullRequest which abstracts git host specific "pull request" things dependent on the host that the repo has been cloned form.

// cloning a repo from github 
const repo = await openRepository("https://github.com/inlang/inlang")
repo.openPullRequest({
  title: "Improve inlang"
})

// or gitlab, bitbucket, etc. shouldn't make a difference
const repo = await openRepository("https://gitlab.com/lisa/client")
repo.openPullRequest({
  title: "Improve inlang"
})

Such abstraction layer seems beneficial for all sorts of apps.

[TazorDE]

I would very much like such a solution. Specifically for Azure DevOps git repositories. This would remove a blocker from using the inlang editor for translation. 😄

[TazorDE]

We currently operate at a relatively small (enterprise) scale. But as we grow our internal and external webapps will most definitely be available in several languages. We are also currently in the process of moving several repositories from service providers to our own (cloud-)infrastructure hosted on azure. We currently crowd-translate in the office, but this takes a lot of developer time and doesn't scale very well. With an editor like inlangs this would definitely improve our scalability regarding the translaton of tools.

[samuelstroschein]

We currently crowd-translate in the office, but this takes a lot of developer time and doesn't scale very well. With an editor like inlangs this would definitely improve our scalability regarding the translaton of tools.

1. Would you be interested in contributing Azure support if we abstract the "git host" APIs into a schema that can to be implemented?
2. Besides the (sveltekit) SDK, are you using other inlang apps like the CLI and ide extension?

We are also currently in the process of moving several repositories from service providers to our own (cloud-)infrastructure hosted on azure.

Own curiosity, what is the incentive to move to own infrastructure?

[TazorDE]

1. I can definitely try to contribute some support, it depends what kind of workload that entails ;)
2. We use the CLI to generate the keys in the translation files but that's it. I have tried the IDE extension but haven't found it very helpful for my workflow yet.

And to satisfy your curiosity: By own infrastructure I meant services like Azure and AWS that we as a company control. Currently a lot of our 'older' projects are hosted by service providers we have contracts with but as we scale up our IT department we want to regain the control over several of those applications and not be bound to always keep using the same service provider. Basically we want the freedom to ditch service providers if we don't like their work and be able to keep the infrastructure running.

[samuelstroschein]

I have tried the IDE extension but haven't found it very helpful for my workflow yet.

What are you missing? (cc @felixhaeberle who is the lead of the ide extension)

Basically we want the freedom to ditch service providers if we don't like their work and be able to keep the infrastructure running.

Understandable. One of the USPs of inlang. Inlang works with your existing data (in a git repo), if our product is unsatisfying, you can switch with no cost :)

[TazorDE]

I'm not really missing anything I just haven't found a benefit in using the extension yet. This may change in the future but as I'm currently creating entirely new services none of the features have caught my eye so far. And the only gripe I have is with the CLI and the automatic translation feature. It merges the JSON structure

"key": {
    "i18nkey": "translation"
}

into a single layer and removes the organisation from the other language files

"key.i18nkey": "translation"

However I saw someone in the Discord already mention this, so I didn't raise the issue much further :)