📝 Problem Statement
Currently, when a user logs a Jap entry, the count is globally synchronized across all active sankalps. This leads to inaccurate data tracking as a user might be performing different Japs for different spiritual goals (e.g., Mahamantra vs. Om Namah Shivay).
🚀 Proposed Solution
We need to decouple the global logging and link each jap_log to a specific sankalp_id.
Key Changes:
🛠 Technical Details
- Table:
jap_logs
- New Column:
sankalp_id (UUID, references sankalps.id)
- Default Behavior: Pre-select the
is_primary sankalp in the dropdown for a seamless UX.
✅ Acceptance Criteria
📝 Problem Statement
Currently, when a user logs a Jap entry, the count is globally synchronized across all active sankalps. This leads to inaccurate data tracking as a user might be performing different Japs for different spiritual goals (e.g., Mahamantra vs. Om Namah Shivay).
🚀 Proposed Solution
We need to decouple the global logging and link each
jap_logto a specificsankalp_id.Key Changes:
sankalp_idforeign key column to thejap_logstable.current_countis only updated for the selectedsankalp_id.🛠 Technical Details
jap_logssankalp_id (UUID, references sankalps.id)is_primarysankalp in the dropdown for a seamless UX.✅ Acceptance Criteria