Add conditional merchant and terminal number fields with validation for operator assignment#551
Merged
Conversation
Member
|
@copilot meant to say dont worry about any testing atm |
…perator assignment Co-authored-by: StuartFerguson <16325469+StuartFerguson@users.noreply.github.com>
Contributor
Author
Understood! I've completed the implementation without running tests. Changes made in commit 19b44d7:
The merchant operator assignment now properly accounts for the RequireCustomMerchantNumber and RequireCustomTerminalNumber flags as requested. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Copilot
AI
changed the title
[WIP] Add validation for merchant and terminal number on operator addition
Add conditional merchant and terminal number fields with validation for operator assignment
Jan 7, 2026
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
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.
Merchant Operator Management - Custom Merchant/Terminal Numbers
Implements conditional merchant number and terminal number input fields when adding operators to merchants in the Blazor Server application. Fields are displayed dynamically based on operator requirements and include validation to ensure proper data entry.
Changes Completed
EstateManagementUI.BlazorServer/Requests/Requests.cs - Updated
AddOperatorToMerchantCommandto include optionalMerchantNumberandTerminalNumberparametersEstateManagementUI.BlazorServer/Components/Pages/Merchants/Edit.razor - Added:
RequireCustomMerchantNumberorRequireCustomTerminalNumberflags are trueOnOperatorSelectedcallback method that dynamically shows/hides fields based on operator selectionValidateOperatorFieldsmethod that ensures:^\d+$)AddOperatorToMerchantmethod to validate fields before submission and pass values to the commandImplementation Details
RequireCustomMerchantNumberandRequireCustomTerminalNumberflagsAddOperatorToMerchantCommandfor processingOriginal Issue
When adding operators to a merchant in the merchant management, the addition needs to account for the required custom merchant number/terminal number flags. If any of these are true against the operator, an edit box to provide these must be available and the field becomes required. The value for either merchant number or terminal number must be numeric.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.