Updates to core, lightspark-sdk, ui #482
Merged
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
## Reason UmaProber does a "probing" against vasps to try to figure out fx exchange rates. Currently when we probe Coins.ph in the Philippines they only have a preferred currency as Tether but we keep mangling the response because we don't have a representation of tether as a currency unit. GitOrigin-RevId: 591ec8a37b23e852e3ec69c32dddc5750a19da3a
- adds mutation to create new umaaas api tokens - shows uma permissions when creating tokens - shows error toasts and state when token info not provided - adds NageModal to be used for token created - updates Modal to use overlayBackground prop instead of voidOverlayBackground - adds CopyInput component for nage - fixes CentralLoadingCircle color - fixes Checkbox background theme color (theme.info)   GitOrigin-RevId: 3ff84388c5cb04bb85265067868e7a025763f857
- adds feature to delete api tokens - updates Table to handle triple dot button columns - updates dropdown component to handle toReactNodesArgs - adds cancel button to NageModal - adds theme for danger button (delete button) - adds card for token display   GitOrigin-RevId: fc011969714490d3541b0b217abe081dca62cee5
 GitOrigin-RevId: fec8ca6cdaae37018643f176f834d464492cc424
|
The following public packages have changed files:
There are 3 existing changesets for this branch. If additional changes have been made that require different versions for any package simply add another 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. The following releases are planned based on the existing changesets:
Last updated by commit 522efa3 |
…194) ## Overview - Implement update name path - Add current user query - Rename update name to update profile per designs GitOrigin-RevId: 6a08f2bc9e63972bd317cda7298fe32b0490e6b2
- adds option to DataManagerTable to save/load filters from URL query params - this allows refreshing the page and persisting filter state - also will be used for the CommandCenter in the future - must be only enabled via boolean because ops pages can have multiple DataManagerTables and we don't want the same filters applying to every table; will need to figure out a solution for that later - fixes date range filter for transactions table GitOrigin-RevId: 0b7220cefe53c79b1eceab0282b95c4d6db965b2
- since umaaas/nage routes live in site, we need to reroute to /umaaas when the user tries accessing any normal cn2 routes - also route to cn2 if the user's roles are not nage related - small fix for zIndex in filter dropdowns GitOrigin-RevId: bfb40937ff165181049b1e877fb49a32608deb80
  Contributes to PX-834 GitOrigin-RevId: 450a09f8bb6befea49d93270fdeb5d4b953415f9
- shows nav items depending on umaaas role - fixes console error due to svg prop - removes notification bell and unused menu items - fixes docs link Admin and developer:  Compliance:  Support:  GitOrigin-RevId: 6435f3e38ff44d0ae9f888bc9baa035a9bd9af08
- use transparent button kind instead of links - add option to Button for justifyContent - add themeable prop for button gap - auto navigate to transactions page if landing on home / base route  GitOrigin-RevId: bb79b901ef7b06f4bbe538c64fce099771913751
- this was a regression when the justifyContent prop was added - it should default to center when not provided GitOrigin-RevId: 3a40a61007ca75b224a4df7f58c1b613a9960215
…r invites (#20341)  GitOrigin-RevId: 5bb91f6ea9c876618ee399e3558e1a54a025949e
GitOrigin-RevId: 9a3ee6ce8d5f395dae9e3fc620774f8c05e8209b
…onfig (#20378)   GitOrigin-RevId: 88c4bd93d79ae47d18450e4be416d846f4be4efb
- adds progress bar loading style to data manager table - adds option to show no loader or progress bar - adds ability to stretch table to match parent component (fullHeight) so that the pagination is at the bottom of the screen and the loader is properly centered when there are no results [Screen Recording 2025-09-10 at 2.40.06 PM.mov <span class="graphite__hidden">(uploaded via Graphite)</span> <img class="graphite__hidden" src="https://app.graphite.dev/user-attachments/thumbnails/f2b95a15-0056-4c63-a0b7-47a297c22bf9.mov" />](https://app.graphite.dev/user-attachments/video/f2b95a15-0056-4c63-a0b7-47a297c22bf9.mov) GitOrigin-RevId: 734257f091069d6cd1d7b3ac3a456d95920ab23c
## Reason This change provides an "uma not allowed in your region" screen if the user's ip is banned when selecting europe during the striga onboarding flow ## Overview * adds a new query to check the current user's ip address against a sanctioned list * modifies the `AddCredentials.tsx` to show a 'uma not allowed' screen as a result of this query * modifies AddCredentials to introduce a more robust state management mechanism ## Test Plan During onboarding of Striga users, set "is ip valid" to false by default on backend, ensure we see the "uma not allowed" screen GitOrigin-RevId: e23f3e750360563e7e1433f4afcf101aec9de1e8
Make the SQL textarea resizable in bobby tables. GitOrigin-RevId: 6d4d64521e3a3a3ff171d243a55820653053d67c
…ync (#20536) ## Reason Explain *why* this change is being made. ## Overview For large or complex changes, describe what is being changed. ## Test Plan Explain how you tested the change. GitOrigin-RevId: d4a54c0b0cfff6e1eaf7481829e70e41c05f84df
  GitOrigin-RevId: 13658f8a6e0e93fea745d4343ab5ba8dad1bb765
GitOrigin-RevId: d3a034f534cfe94103d7c79dadab1d747a7280f2
## - Created a new UI for the LinkBankINR component with a form for users to enter their UPI ID - Added necessary translations for UPI-related text in English, Spanish, and Portuguese - Implemented validation for the UPI ID field - Added conditional rendering based on Tazapay integration status and user onboarding state GitOrigin-RevId: 6f91c0bc5c3eb85d5da26bbe5f963fc3cd430a9e
## Reason closes PX-776 Implement update iban page for Striga users This flow is for users who have already provided an IBAN and need to change it. This flow is somewhat complex, as it requires users to first cancel an existing standing order * add UpdateBankEu component for remove/update iban * connect to cancel standing order mutation * link the settings page update/remove bank account buttons to this new component * link the received failed indicators to UpdateBankEu This code shares quite a bit of functionality with link bank eu, so this PR also extracts common functionality into shared components GitOrigin-RevId: 075eadae3e36ec6d65a2a99500beb9e218049613
- fixes wonky auto date application logic with Apply button
- use shouldClose={false} to avoid styling issues when clicking a date range
- fixes typography of calendar text
GitOrigin-RevId: dd26ad67bbd061ae1ba9b5ccd4adf249d5f3cdf5
Update public `js` sources with the latest code from the [public repository](https://github.com/lightsparkdev/js-sdk) main branch. This typically happens when new versions of the SDK are released and version updates need to be synced. The PR should be merged as soon as possible to avoid updates to webdev overwriting the changes in the js-sdk develop branch. --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Matt Davis <matthappens@gmail.com> Co-authored-by: Peng Ying <peng@lightspark.com> Co-authored-by: lightspark-ci-js-sdk[bot] <134011073+lightspark-ci-js-sdk[bot]@users.noreply.github.com> Co-authored-by: Lightspark Eng <engineering@lightspark.com> Co-authored-by: Corey Martin <coreyn.martin@gmail.com> GitOrigin-RevId: 6578b59e40e43022573e22ffa9d57bb1358262cf
pengying
approved these changes
Sep 20, 2025
matthappens
approved these changes
Sep 20, 2025
- fixes enum rendering in menu and pill filters - wraps filter pills in header - fixes string and id filters getting reset upon adding the filter again    GitOrigin-RevId: 2228ef78b37309d968b5d3b931b909f65a4cd77a
coreymartin
changed the title
pengying
approved these changes
Sep 20, 2025
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.