Adds a listitem renderer overwrite to marked which
wraps everything that is inside a <li> which isn't only single <p> tag
into a <div class="list-content"> which we give a margin: 1rem 0;
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
- 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>
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 looks like there was maybe a regression at some point and
we lost the colors on the code and blockquote blocks. This adds
them back. We also give blockquotes some padding like regular
paragraphs.
Signed-off-by: Alexis Sellier <self@cloudhead.io>
Moving the theme toggle inside a settings dropdown in-place.
Adding a switch for the used monospace font, user can either use the
OS or browser default, or switch to "JetBrains Mono".
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
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>
- add a link to the faucet page from `Rinkeby` badge in header
- refactor the `<TextInput>` component to include
- a loading indicator
- a keyboard shortcut to submit the input by pressing the `enter` key
- add a keyboard shortcut hint <kbd>⏎</kbd> that shows up whenever the
input is ready to be submitted
- a validation message
- align all pages with a single input form to have a similar look and feel
- improve validation messages and error handling in all forms
Signed-off-by: Rūdolfs Ošiņš <rudolfs@osins.org>
- type events that are handed between components
- simplify the `resolve` function interface
- before we had return values and exceptions, now just a single union
type as return value
- move navigation to the Search component to reduce its
responsibilities
- flatten and simplify multi-level branching
- shuffle around code
- move the `resolve` function to the `Search` component module,
because it's only used there
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>
Sebastian Martinez