ecamp / ecamp/ecamp3

Separate camp location per period

Open
#10,130 0 comments 1 reaction 0 assignees View on GitHub
Feature request type: API type: Frontend type: Print
Dominant language
PHP
Stars
156
Forks
72
Avg merge
12h 43m
Merged PRs (30d)
203

Description

In most multi-period camps, the location information is not shared between the periods. However, historically, we have had only one set of location fields on the camp. These fields could be moved to the period entity.

Contributor guide

Open the contributing guide

Research direction

Start by locating the camp and period entities and identify the existing camp-level location fields. Determine which location data must become period-specific, then trace the affected camp and period behavior to define the required model and persistence changes; done means each period can hold its own location without sharing it unintentionally.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend, database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.