chore: improve cf deployment flow#293
Open
IzioDev wants to merge 100 commits into
Open
Conversation
- refactor component a tad
## what? re-designs the presentation of the toasts (from being just a screen list) to having some depth. shows a max of 3 at a time. gives some nice(r) animations etc. <img width="468" height="187" alt="image" src="https://github.com/user-attachments/assets/328ec0b6-1929-4219-bc30-91b32d505712" /> ## test: add something like this to message provider to spam a whole bunch of toasts: ``` useEffect(() => { const toastTypes = ["success", "error", "warning", "info"]; const generateRandomMessage = () => { const length = Math.floor(Math.random() * (100 - 5 + 1)) + 5; const chars = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 "; let result = ""; for (let i = 0; i < length; i++) { result += chars.charAt(Math.floor(Math.random() * chars.length)); } return result; }; const interval = setInterval(() => { const randomType = toastTypes[Math.floor(Math.random() * toastTypes.length)]; toast[randomType](generateRandomMessage()); }, 1000); return () => clearInterval(interval); }, []); ``` ## what else? adds donation address to the logged in settings screen adds toast for message import import (initiate and completion) adjust hold-able + button remove toast removal on all route changes reduce toast duration on mode switch
## what? adds network connection indicator on mobile (top overlay) and desktop (right hand side) red is disconnected yellow is disconnected and connecting green is connected (and fades in 5s)
This should fix stale cache
## what? updates the use of the term 'wallet' to 'account' in user facing components. mainly to lower the conceptual barrier and not to lead people into thinking kasia should be used as a wallet. note: not worth doing this to our internal components. I think its a fine abstraction.
## what? adds 'pending, active, failed' message status to direct messages and payments. follows the current broadcast approach. handshakes have _not_ been done as they are a little more complicated. followup tasks from this: - add custom fees to 'payments' (custom fees should exist for wallet withdrawals and handshakes as well, but payments should have some urgency due to its UX) - extend status into handshakes - add rbf for pending tx - refactor message ingestion once vccv2 is out in the real world
wip: block lists refactor: tidy settings menu feat: further bcast chore: color, component name fix: misc - tidy up var names - some styling - load block list before handshakes - really make sure we dont get handshakes for blocked messages feat: add generic confirmation modal refactor: block core functionality - all blocks are now block and delete - lift method to store feat: add default channel feat: move blocked button on directs to contact list feat: multiple items - post rebase cleanup - delete blocked-store for tenant ID - add import export for blocked addresses - bring settings modal into modal system style: transition new chat instead of present new modal style(fix): remove redundant conditional on locked home
## what? initial 'block a contact' feature adds: ability to block from broadcasts or directs contact info pane ability to see blocked addresses and a broadcast vis option in settings stores the blocked address in db (also has the capacity for a 'reason') - note: my initial version included a reason field and allowed users to block an address straight from the settings, but I removed this as it was a little complicated handling the visibility states etc. So atm, we have no UI to add a reason and no way to block a contact unless its on their contact card. blocking will delete any in db contact or messages. BUT in bcasts you will either still see a "Blocked Contact" message or no message (depending on your settings) also adds `kasia-general` as a default initial channel. users can block now so this seems reasonable?
- move markdown rendered to own component
- add conditions on broadcast image and link rendering - add alert to link navigation - refactor/chore: remove rehype and clean up md renderer
## What? adds markdown rendering to messages by default, all clients will render Markdown messages if they include the `MARKDOWN_PREFIX = "§"`. However, to send markdown messages, you must enable it via a feature flip. This is because of the higher cost etc. with rendering enabled, broadcasts do not render links or images by default. This must be enabled separately as a sub-feature. In direct messages, links and images are always rendered. currently we (I) are only planning to support the base CommonMark standard. As I *personally* don't think a chat app needs rich github level markdown features. There is also no UI interface to interactively place markdown or to see the markdown as you write it, maybe this can happen in future versions (item 2 here being of more importance than item 1) . <img width="741" height="923" alt="image" src="https://github.com/user-attachments/assets/04deb6c3-0353-42de-8fcd-c84dae514d99" />
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No more UI opening.