Samuel Stroschein

@janfjohannes `parseOrigin` doesn't exist on the repo API, nor is it exported from lix though. **context** - `getOrigin` is not suited as `parseOrigin` replacement. `parseOrigin` acts as `stripOriginFromMetadata` (good rename!)....

@janfjohannes does the following clarify the intent? #### `repo.getOrigin()` gets the unfiltered origin as stated in the repository. if we process it, it will become useless in envs where metadata...

@NiklasBuchfink 1. agree? 2. I assigned you because @flornkm is gone. If you implement it for Fink, you should be able to re-use the logic for manage and badge too

## Proposal 1 - Change subscribable to an object getter That's how Preact signals work https://preactjs.com/guide/v10/signals/. We can expose the `.value` property in the project API. ```diff - project.errors() +...

@martin-lysk @janfjohannes curious about your input regarding the proposal above. another proposal is also welcome. a bummer that JS reactivity is not standardized. @martin-lysk please do not open a discussion...

I will update the issue on the problem later today. The issue is unrelated to the implementation. The API we expose of Subscribable is of high risk for breaking changes.

I will update the issue after I implemented the directory proposal.

reply to @janfjohannes https://github.com/opral/monorepo/issues/1680#issuecomment-1821478152 > but i still think we should not poolute lix with any framework specific reactivity concepts [...] > to adapt this to whatever framework reactivity system...

We partially made the right design decision by settling on functions. Good: - static access like `project.errors` does not work. at any given time an async computation could occur from...

> @janfjohannes i think the next step is to add the changeset workflow into our own ci as the github action runner we use at the moment is very slow,...