[trivial] Updated description for tasks.site.
## Reason
This was copied from
#490
Conversation
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
## Reason This was copied from minikube so they were rendering on the same line in shell completion. ## Test Plan N/A. GitOrigin-RevId: ba66c0264c979d30eea5a1ee8ae14477b0b278d1
Contributor
Author
|
The following public packages have changed files:
There are no existing changesets for this branch. If the changes in this PR should result in new published versions for the packages above please add a changeset. Any packages that depend on the planned releases will be updated and released automatically in a separate PR. Each changeset corresponds to an update in the CHANGELOG for the packages listed in the changeset. Therefore, you should add a changeset for each noteable package change that this PR contains. For example, if a PR adds two features - one feature for packages A and B and one feature for package C - you should add two changesets. One changeset for packages A and B and one changeset for package C, with a description of each feature. The feature description will end up being the CHANGELOG entry for the packages in the changeset. No releases planned. Last updated by commit fee46bb |
…#22309) ## Reason Sofi wants the ability to filter operations by failure reason ## Overview - since we have separate enums for send and receive operation failure reasons, I split it into two filters - makes send/receive specific queries if send/receive failure reason filter is present - common filter logic is abstracted - adds callback to DataManagerTable to handle reacting to filter state changes - makes "type" and failure reason filters mutually exclusive since it doesn't make sense to have multiple applied at the same time - updates unit tests ## Test Plan - unit tests - works locally   GitOrigin-RevId: f74ca29c2593d95f55b52ce518cc26e9ad8cf1a3
## Reason The current phone number validation regex is too restrictive, only accepting US 10-digit phone numbers that start with digits 2-9. This prevents international phone numbers and other valid formats from being accepted. ## Overview Updated the phone number validation regex to accept phone numbers with 7-15 digits, accommodating international phone number formats and a wider range of valid phone numbers. ## Test Plan Tested by verifying that: - Valid international phone numbers with varying lengths (7-15 digits) are now accepted - Phone numbers with fewer than 7 or more than 15 digits are rejected - The form validation works correctly with the new regex pattern GitOrigin-RevId: 4ca3c2f5cd975b5760cf67dcd8677c88a0594c10
## Reason Shakepay needs this for remote signing so that they can fail back HTLCs that don't wish to claim. ## Test Plan Unit tests. GitOrigin-RevId: 846ac06b9ceb53bb9512dd2025219e3006f2be3e
## Reason No reason [https://app.graphite.com/github/pr/lightsparkdev/webdev/22418/[ops]-add-core-service-select-in-header-instead-of-toggles#comment-PRRC_kwDOHaFZpc6bdfkz](https://app.graphite.com/github/pr/lightsparkdev/webdev/22418/%5Bops%5D-add-core-service-select-in-header-instead-of-toggles#comment-PRRC_kwDOHaFZpc6bdfkz)   GitOrigin-RevId: b23d54f17da86fbe14386c1d3b7e554caaa261e8
## Reason sumsub kyc modal was overflowing and wasn't scrollable completely ## Overview - makes Drawer more scrollable and fixes paddings (unrelated) - fixes kycsumsubmodal scrolling ## Test Plan  GitOrigin-RevId: 5f1f9e30d7bca379c65fe1414722d0bd9de418ff
## Reason Add 4 new African currencies GitOrigin-RevId: a5d4983b76a0522ebca873576b349ee047a0cb60
## Reason we were seeing long button text stretch the button past modal screens ## Overview - adds overflow hidden to button so that ellipsis works properly for full width - updates translations for "Open email app" so that it fits ## Test Plan  GitOrigin-RevId: 3426847249ce63cc99bab48c8a4d41036140e6bb
## Reason Updated design to be clearer ## Overview - adds scroll up button - adds text - adds new icons ## Test Plan   GitOrigin-RevId: 61a0ed2d6f115e014456a414fd4f36a424f10e34
## Overview - minor fixes for the link bank UI and copy changes ## Test Plan     GitOrigin-RevId: 7c380f30fe882496802e22fee1f1480348c20f35
## Reason On iOS there's a usability issue with Drawers where there's "scroll bleed" causing - scroll to go below the modal overlay/background - the drawer starts too high ## Overview - fixes the scroll bleed with a new hook that locks scroll - moves drawer to be above keyboard with another hook that listens for the offset - note: top overrides bottom set by the keyboard offset so modals with top will stick to the top which is intentional - refactors NationalitySelector so that VerifyIdentityModal can show its contents within the same modal - various other fixes downside is you can no longer touch move the outer drawer container so if it's too large the user won't be able to see the top ## Test Plan [Screen Recording 2025-12-16 at 7.06.59 PM.mov <span class="graphite__hidden">(uploaded via Graphite)</span> <img class="graphite__hidden" src="https://app.graphite.com/user-attachments/thumbnails/1e9de009-90f5-4f2e-9cd9-c03bf055601f.mov" />](https://app.graphite.com/user-attachments/video/1e9de009-90f5-4f2e-9cd9-c03bf055601f.mov) GitOrigin-RevId: 24e1bdeb942ac5138d027b82069f90d312c09234
## Reason Several design / functionality issues came up during Striga's recent design review, here are a few of them | Change | Appearance | |----------|----------| | new icon for proof of address & secondary text color for subtext |  | | remove us error subtext |  | | check all banned countries when determining eligibility requirements | previously we relied on IP check - this update makes it so that we block countries like Russia even when they do not have russian vpns. | | Fix rejected final icon & text centering |  | |add loading state and spinner to continue | | GitOrigin-RevId: 5fd335913073ab0d07214666beb4de0dcf2a5d86
## Reason closes PX-1305 Nigeria has a dedicated "can't link your bank" page for name match failures This PR adds that page ## Changes * Add a "yellowcard error" enum which is included as part of the bank info output. For now, it only indicates a failure to match names * if the client sees this error, display the new page, which will redirect back to link bank in case the user wants to try again  GitOrigin-RevId: c0662e2cbd878da72d07f75654e48b9ee3a54714
- Add symlinks from all CLAUDE.md files to AGENTS.md so that they get seen by all agent types (including cursor). - Switch the cursor rule structure to the new file format: https://cursor.com/docs/context/rules#project-rules - Clean up a few of the rules for formatting and details. GitOrigin-RevId: 5b0bb0ed7e60248fd7c83be92b6a5b24b5c71df8
…at (#22727) ## Reason We mainly only had events for the zerohash onboarding flow and were generally missing a lot of events. This adds events from https://docs.google.com/document/d/1jxW4cKvoyK8k-L7eDEMi_xg65iYqc6pQl1RdyAvLwGA/edit?tab=t.uzinptq1apsn and more ## Overview - adds events - rather than region-specific event names, have generic events and have accountType be a parameter in certain cases - reformats existing events to follow the same pattern (no colon prefix, and action properties) ## Test plan tested locally GitOrigin-RevId: 40fac5de2b9af8072c2ff44d1d156b448d9875ab
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If this change should result in new package versions please add a changeset before merging. You can do so by clicking the link provided by changeset bot below.