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

MLPAB-2731: Add material and immaterial change confirmed events #122

Merged
merged 1 commit into from
Feb 12, 2025

Conversation

acsauk
Copy link
Contributor

@acsauk acsauk commented Feb 5, 2025

Enables MLPAB-2731 and MLPAB-2732.

@acsauk acsauk force-pushed the MLPAB-2713-add-material-immaterial-change-events branch 4 times, most recently from 371d034 to 264cac3 Compare February 5, 2025 17:25
@acsauk acsauk marked this pull request as ready for review February 5, 2025 17:30
@acsauk acsauk requested review from a team as code owners February 5, 2025 17:30
Comment on lines 23 to 27
"if": {
"properties": {
"actorType": { "const": "attorney" }
}
},
Copy link
Contributor Author

@acsauk acsauk Feb 5, 2025

Choose a reason for hiding this comment

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

This is in preparation for tickets like this but happy to drop if we'd rather keep this targeted at donors and CPs for now.

Copy link
Contributor

Choose a reason for hiding this comment

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

I feel like it might be simpler to always have actorUID, even if we don't really need it

"description": "The UID of the actor that made the change",
"pattern": "^([a-z0-9]{8}-)([a-z0-9]{4}-){3}([a-z0-9]{12})$"
}
},
Copy link
Contributor

Choose a reason for hiding this comment

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

Q for Sirius people: will marking this as a material change trigger some communication we could include the date of in here? Since we want to have "We contacted you on {{.Date}} with guidance about what to do next." displayed, it would be nice to have the sent date

@acsauk acsauk force-pushed the MLPAB-2713-add-material-immaterial-change-events branch 3 times, most recently from a907fd2 to f83e260 Compare February 10, 2025 11:30
@acsauk acsauk merged commit f6d5828 into main Feb 12, 2025
1 check passed
@acsauk acsauk deleted the MLPAB-2713-add-material-immaterial-change-events branch February 12, 2025 16:47
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