Cycle Generation System closes #277 #290
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
UX research
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
Depends on
#291 Membership Fee Type Resource & Settings closes #278
local-it/mitgliederverwaltung
#284 Calendar Cycle Calculation Logic closes #276
local-it/mitgliederverwaltung
Reference: local-it/mitgliederverwaltung#290
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/277_cycle_generation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of the implemented changes
The changes were:
Definition of Done
Code Quality
Accessibility
Testing
- Handle Task crashes in async_stream with {:exit, reason} - Return {:error, {:partial_failure, successes, errors}} when some cycles fail - Previously returned {:ok, successful} even on partial failures - Improves debuggability and allows callers to handle partial failures82897d5cd3to5acf4364fa5acf4364fatoed083830b9Nice work :)
Just the small thing with the docs.
And I asked myself if it might be performance wise an issue if a lot of members are imported the first time...
@ -80,7 +80,7 @@ defmodule Mv.Membership.Member doargument :user, :map, allow_nil?: true# Accept member fields plus membership_fee_type_id (belongs_to FK)@ -12,2 +12,4 @@- `member_field_visibility` - JSONB map storing visibility configuration for member fields(e.g., `%{"street" => false, "house_number" => false}`). Fields not in the map default to `true`.- `include_joining_cycle` - Whether to include the joining cycle in membership fee generation (default: true)- `default_membership_fee_type_id` - Default membership fee type for new members (optional)Good idea!
@ -0,0 +128,4 @@- Has a membership_fee_type assigned- Has a join_date set- Is active (no exit_date or exit_date >= today)We thought about payment status "suspended", should we keep that in mind somehow?
The suspended status is implemented in another issue