Use Bridge NPM Package#1148
Open
tiksn wants to merge 5 commits into
Open
Conversation
ashotnazaryan
approved these changes
Mar 30, 2026
tiksn
force-pushed
the
use-bridge
branch
7 times, most recently
from
6c8e36c to
1ad89c1
Compare
tiksn
force-pushed
the
use-bridge
branch
7 times, most recently
from
e1e29f9 to
daae003
Compare
tiksn
force-pushed
the
use-bridge
branch
10 times, most recently
from
974eef5 to
59b1263
Compare
tiksn
force-pushed
the
use-bridge
branch
3 times, most recently
from
ab4b5dd to
46e03c0
Compare
tiksn
force-pushed
the
use-bridge
branch
3 times, most recently
from
5020673 to
e712867
Compare
tiksn
force-pushed
the
use-bridge
branch
8 times, most recently
from
1689880 to
29accd6
Compare
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
2 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.
Summary
This PR moves the UI onto the shared Fossa Bridge API contract so frontend behavior stays aligned with the backend-facing client model.
The goal is to preserve the existing app experience while standardizing API-backed flows across authentication, entity management, onboarding, offboarding, licensing, profile, and company settings. It also updates the surrounding error and response handling so the UI continues to surface failures consistently after the migration.
Validation
Coverage has been updated for the affected API-backed flows and Bridge response handling.