We just use the radicleExplorer that is configured in the app config and
don't query the node for it. Besides simplifying things this also makes
the button work on iOS again, because we don't have the async http
request anymore.
Since the legacy config is being deprecated at the end of 2024, we
should start moving to the eslint flat config.
I avoided the tseslint config helper function so we avoid wrapping
magic.
This seems to have triggered more checking since any checks in svelte
files have appeared and the $$Generic type that is being deprecated had
to be rewritten.
Also fixes some any types that weren't caught previously
- Handle ResponseParseErros, ResponseErrors and normal errors
differently.
- Show them all in the same `LoadError` view
- Add a subtitle to give users some more information on what could have
gone wrong.
- Add more properties to the copyable error message to make debugging
easier.
Following the heartwood release 6ca7da2 we also rename tracking
to seeding, and update our `radicle-httpd` endpoints and configs.
Also updates test suites to handle new CLI commands.
We elminitate the element with the “button” role that wrapped the
Popover toggle slot. The element rendered into the slot is in all cases
already a button. This prevents issues where `getByRole("button")` finds
_two_ buttons for popover toggles.
We take the opportunity to simplify the popover toggling by making the
slot responsible for the toggle. This has a couple of advantages:
* We don’t need a `disabled` property for Popover. This is handled by
the button. (This fixes a bug we did not disable the PeerSelector
Popover properly.)
* The popover is opened on key events
In the future this also gives us more flexibility in determining how to
toggle the Popover.
Signed-off-by: Thomas Scholtes <geigerzaehler@axiom.fm>
Also does some refactoring for `action`, `editable` and other variables
we were using which weren't very clear
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
We simplify the properties of the project views `Issue`, `Issues`,
`NewIssue`, and `Patch`. This aligns them with other project views and
makes the view selection consistent.
Signed-off-by: Thomas Scholtes <geigerzaehler@axiom.fm>
We still allow already published URLs with `/seeds/` in them to be
resolved.
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
Signed-off-by: Rūdolfs Ošiņš <rudolfs@osins.org>
We switch to a project route type that is just a union. This has the
following advantages
* It’s much easier to construct project routes. Fewer properties are
needed and there are no nested objects.
* We eliminate the implicitly shared properties `path`, `peer`,
`revision` and `route` which only belonged to the tree route.
* The structure of the project route is more regular and thus easier to
understand.
Signed-off-by: Thomas Scholtes <geigerzaehler@axiom.fm>
- Patches listing
- Patch detail view
- Ability to switch between patch revisions
- Add or remove tags from a patch (if logged in)
- See the following information on a patch
- Title
- State
- Author of first revision
- Timestamp of creation of first revision
- For each revision a user can see
- Merges
- Reviews (accepted, rejected or just commented, no inline code comment support yet)
- Comments on Reviews if available no code comments yet
- See related commits
- A changeset over the entire revision
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
There were some issues in how we handled the state param in the url
querystring in the issue and patch listings.
This commit should improve this, and allow for better usage of
querystring params in the future.
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>