Skip to content

Release Note (portal): Test release notes automation #183

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.

Sign up for GitHub

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

Closed
fiskaltrust-release-notes-bot wants to merge 1 commit into from
Closed

Release Note (portal): Test release notes automation #183

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions portal/test-release-notes-automation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
---
title: "Test release notes automation"
source: https://github.com/fiskaltrust/service-portal-ui/issues/273
milestone: "n/a"
date: 2026-03-30
labels: []
---

## Summary
The editing process for PosOperator invitations has been upgraded to a new React form, enhancing user experience with inline validation and faster updates.

## Why This Matters
This change allows PosDealers to review and adjust invitation details more efficiently, eliminating the need for full page reloads and reducing friction when correcting data.

## What Changed
- Transitioned the PosOperator invitation editing from MVC to a React-based form.
- Implemented an `EditPosOperatorInvitationPage` that prepopulates dynamic company/user field groups.
- Updated navigation to the React edit route based on feature flag status.
- Ensured API parity by reusing the same endpoints for fetching and updating data.
- Added unit/integration tests for the new React edit component and API contract tests.

## Impact
PosDealers will benefit from a more streamlined editing process. No action is required from users; the transition to the new React form will occur automatically when the feature flag is enabled.
Loading