This now allows setting `GIT_HEAD` "from the outside" and will
gracefully fall back to "unknown" in case there's any issue figuring out
what HEAD refers to.
- by default open repos on the home view
- show a rendered README on the repo home page
- show repo metadata: visibility, canonical branch, threshold, delegates
and allow list with aliases
- make layout responsive on repo home
- add copy button to code blocks in markdown
So we don't materialize the whole list multiple times especially when
paginating. Mostly written by Finto, I was just driving.
Co-authored-by: Fintan Halpenny <fintan.halpenny@gmail.com>
This commit allows us to e.g. convert the Set of DIDs we obtain from
assignee actions on cobs into a Set of Authors with their Aliases.
Also it introduces the `FromRadicleAction` trait which can be
implemented for any type of enum we get from the `radicle` create to
convert into a type which is better suited for us.
Removes also any calling the `alias` command in the `PatchTimeline` or
`IssueTimeline` since we already get the alias from the backend the
first time now.
This allows us for onboarding to e.g. fail if there is no profile around
and guide new users through identity creation.
Also it makes the tauri run function easier to understand
@fintan:
The API of the DraftStore needs some improvement and it can be easy to
do the wrong thing when trying to publish the changes to the published
cob reference
Based on this PSA we should apply any changes to the patch revisions
directly, instead of using the `DraftStore`
By restricting `img-src` in our CSP, we weren't allowing images from
e.g. https://github.com like CI badges to display.
With this change we allow users to add images from any `https`, `data`
or `blob` source, which is more user friendly.
`Show::All` which is the default value should return all values obtained
from `storage.repositories()`.
This commit adds a `Show::Contributor` enum variant to only get repos
that the user has forked, initialized or contributed in some way.
To start making the backend codebase more future proof, I started
introducing the hexagonal architecture concept, of having `Service`
traits that is the public API and inner traits like `Storage`,
`Metrics`, etc. that can be implemented by different adapters like
`Sqlite`.
This is a first development in this direction.
Sebastian Martinez