Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LCFS-1453: Legal name of transaction partner #1489

Merged
merged 2 commits into from
Dec 18, 2024

Conversation

areyeslo
Copy link
Collaborator

BCeID user cannot add her/his own organization as Transactional Partner in Allocation Agreements and Notional Transfers:

Legal name of transaction partner not showing own organization:
image

When BCeID user type own organization, then an error is displayed:
image

Story

Copy link

github-actions bot commented Dec 18, 2024

Frontend Test Results

  1 files  ±0  116 suites  ±0   39s ⏱️ ±0s
390 tests ±0  367 ✅  - 3  20 💤 ±0  3 ❌ +3 
392 runs  ±0  369 ✅  - 3  20 💤 ±0  3 ❌ +3 

For more details on these failures, see this check.

Results for commit 82a4ed6. ± Comparison against base commit 3187c52.

♻️ This comment has been updated with latest results.

Copy link

github-actions bot commented Dec 18, 2024

Backend Test Results

501 tests  ±0   501 ✅ ±0   1m 53s ⏱️ +2s
  1 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit 82a4ed6. ± Comparison against base commit 3187c52.

♻️ This comment has been updated with latest results.

Copy link
Collaborator

@AlexZorkin AlexZorkin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just one console log cleanup.

@areyeslo areyeslo force-pushed the LCFS-1453-LegalNameOfTransactionPartner branch from 4b92952 to bce3579 Compare December 18, 2024 16:39
@areyeslo areyeslo merged commit 5fa0ddc into release-0.2.0 Dec 18, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants