You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: prevent ToggleGroup deselection in single mode
ToggleGroup now implements proper radio button behavior by default,
preventing deselection and ensuring one option always remains selected.
Remove redundant protection logic from individual usages.
fix(settings): weight unit toggle now marks form as dirty
- Add shouldDirty: true to setValue calls in handleUnitChange
- Ensures Save Settings button is enabled when unit preference changes
docs: clarify commit message guidelines to prevent duplicate changelog entries
Copy file name to clipboardExpand all lines: docs/steering/conventions.md
+39-18Lines changed: 39 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,34 +121,55 @@ Follow conventional commit format with these TrendWeight-specific rules:
121
121
-`test:` - Adding or updating tests
122
122
-`chore:` - Maintenance tasks, dependency updates
123
123
124
-
#### Multi-Topic Commits
125
-
When a single commit spans multiple major unrelated areas, use footers to document each major topic:
124
+
#### Single vs Multi-Topic Commits
125
+
126
+
**Single Topic Commits (Preferred)**
127
+
Most commits should focus on one specific change:
128
+
129
+
```
130
+
fix: settings form not marking dirty when weight unit changes
131
+
132
+
Add shouldDirty: true to setValue calls in handleUnitChange to ensure
133
+
the Save Settings button is enabled when unit preference changes.
134
+
```
135
+
136
+
**Multi-Topic Commits (Use Sparingly)**
137
+
Only when you have multiple genuinely UNRELATED changes that must go together, use footers:
126
138
127
139
```
128
-
feat: implement backend computation with UI improvements
140
+
feat: add user authentication system
129
141
130
-
Add server-side weight trend calculations and fix several frontend issues.
142
+
Implement core authentication with JWT tokens and user registration.
131
143
132
-
feat(api): add MeasurementComputationService for server-side trend calculations
133
-
- Implement exponentially smoothed moving average (alpha=0.1)
134
-
- Add ComputedMeasurement and SourceMeasurement models
135
-
- Update MeasurementsResponse to use computedMeasurements array
136
-
- Support optional includeSource parameter for raw data access
144
+
fix(api): resolve memory leak in background sync process
145
+
- Dispose HttpClient instances properly
146
+
- Cancel long-running tasks on shutdown
137
147
138
-
refactor(web): improve progress tracking system
139
-
- Centralize toast management in SyncProgressProvider to prevent duplicates
140
-
- Simplify useSyncProgress API by hiding internal functions
141
-
- Remove redundant useSyncProgressId hook
142
-
- Fix React hooks rule violations with proper useWithProgress wrapper
148
+
docs: update deployment guide with new environment variables
149
+
```
150
+
151
+
**Critical Rules:**
152
+
-**Main message describes ONE specific change**, not a summary of multiple changes
153
+
-**Only use footers for additional UNRELATED changes** that deserve separate changelog entries
154
+
-**Never create a footer that restates the main message** - this creates duplicate changelog entries
155
+
-**If all changes are related, group them under the main message without footers**
156
+
157
+
**Bad Example (creates duplicate changelog entries):**
158
+
```
159
+
fix: improve form behavior
143
160
144
-
fix(web): download page skeleton width now matches actual table dimensions
161
+
Fix multiple form-related issues.
145
162
146
-
docs: restructure documentation with steering documents and commit guidelines
163
+
fix(forms): settings form not marking dirty when weight unit changes
147
164
```
148
165
149
-
Only use footers for major topics - group related changes together rather than creating a footer for every small change. Footers can be multi-line to provide details.
166
+
**Good Example:**
167
+
```
168
+
fix: settings form not marking dirty when weight unit changes
150
169
151
-
**Important**: Don't create footers that simply restate the main commit message. Only use footers when you have genuinely different types of changes that deserve separate changelog entries.
170
+
Add shouldDirty: true to setValue calls in handleUnitChange to ensure
171
+
the Save Settings button is enabled when unit preference changes.
172
+
```
152
173
153
174
#### Rules
154
175
-**Never use "BREAKING CHANGE"** - this is an application, not a library
0 commit comments