Since we don't have or want any deployments on IPFS, and we don't have
much use for hash routing else, we can clean up some code and remove
some tests.
- 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.
Previously the theme was only loaded when the <ThemeSettings> component
was loaded in the footer. This stopped working since we removed the
layout around the loading spinner.
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>
This improves UX making it easier to find the tab that I'm looking for
when I have multiple tabs open.
Signed-off-by: Rūdolfs Ošiņš <rudolfs@osins.org>
Also moves the HASH_ROUTING env variable from being modified inside the
hashRouter.spec.ts into the webserver config in the
playwright.config.ipfs.ts
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
When loading a ETH address as vesting contract we show a cryptic error
message, which non tech-savy end users don't understand, this commit
changes it to something more human readable.
We allow users to enter and load a contract that probably isn't a
vesting contract.
The `getInfo` function in the `vesting` folder is very prone to possible
errors, and benefits from some parallelization between all the method
calls.
We allow hereby to enter a contract address in search and once on the
contract profile page we provide a link to the detailed vesting
information if available.
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
It's not working with our current seed nodes and is confusing to users.
It also prevents us from upgrading transitive dependencies.
Signed-off-by: Rūdolfs Ošiņš <rudolfs@osins.org>
This allows people to either search for their vesting contract through
the search form or visit directly `vesting/<contract address>`
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
Playwright is more flexible and has better developer experience than Cypress.
We add end to end tests covering:
- project source browsing
- tree view
- commit list view
- commit view
- routing
- hash based
- history API based
- clipboard copy paste functionality
- seed view
- project search
- landing page view
- settings
Co-authored-by: Sebastian Martinez <me@sebastinez.dev>
Signed-off-by: Rūdolfs Ošiņš <rudolfs@osins.org>
To provide the same emoji experience on all browsers and OS we use
Twemoji and replace all emojis where possible.
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
Move constants that are tightly coupled to the implementation of
features and unlikely to change or be user configurable out of `config.json`.
Decouple configuration from wallet state.
Signed-off-by: Rūdolfs Ošiņš <rudolfs@osins.org>
We only use it in one place anyway. And components should be
self-contained, so they're easier to reason about.
Signed-off-by: Rūdolfs Ošiņš <rudolfs@osins.org>
- Move all global typography styles to its own file. This makes it
easier to find all the typography related definitions for newcomers.
- Prefix all typography related global CSS classes with a unique prefix
`.txt-`. This allows us to grep the codebase and see exactly where
they are applied. Another benefit of this convention is that it helps
to avoid accidentally mixing global and local styles. Having global
CSS classes that sometimes overlap with component CSS classes makes it
very hard to reason about the resulting visuals and making changes
unpredictable.
- Introduce CSS variables for standardised typography sizes and apply
them to the whole codebase consistently. This way we can adjust the
size in one place and it will be applied everywhere.
- Avoid using predefined HTML tags which might have differing styling
from browser to browser, e.g. `<h1>`, `<strong>`. We should stick to
applying styling either by adding a specific global CSS class or using
the predefined CSS variables, this way we can be sure that the styles
won't be overridden by browser defaults.
- Have a minimal set of modifiers `.txt-monospace` and `.txt-bold` and
apply them consistently. Since `.txt-monospace` is defined via a CSS
variable, we'll be able to switch out fonts via a user setting in the
future.
Signed-off-by: Rūdolfs Ošiņš <rudolfs@osins.org>