feat: per-user voltage color thresholds#327
Merged
Merged
Conversation
Stores optional warning/critical voltage thresholds per user and sensor,
letting the client color a voltage reading. Thresholds are unset by default
(no coloring until configured).
- UserSensorVoltageThreshold entity (composite key UserId+SensorId), DbSet and
fluent config mirroring UserSensorCustomName, with an EF migration.
- PATCH/DELETE /sensors/{id}/voltage-thresholds, access-gated, validating that
warning is above critical.
- WarningVoltage/CriticalVoltage merged into SensorDto in GetAllSensors and
GetSensor so the list carries them without an extra round-trip.
- Cleared on unclaim and account deletion, and included in the data export.
Merged
sondresjolyst
pushed a commit
that referenced
this pull request
Jun 29, 2026
🤖 I have created a release *beep* *boop* --- ## [2.10.0](v2.9.3...v2.10.0) (2026-06-29) ### Features * per-user voltage color thresholds ([#327](#327)) ([fb0f73e](fb0f73e)) ### Dependencies * bump `actions/checkout` from 6.0.3 to 7.0.0 ([#321](#321)) ([8dcdf7f](8dcdf7f)) * bump `equinor/ops-actions/.github/workflows/docker.yml` from 9.38.2 to 9.38.3 ([#322](#322)) ([0841383](0841383)) * bump `equinor/ops-actions/.github/workflows/release-please-manifest.yml` from 9.38.2 to 9.38.3 ([#320](#320)) ([30ee43b](30ee43b)) * bump `PuppeteerSharp` from 25.1.0 to 25.1.2 ([#323](#323)) ([1330f89](1330f89)) * bump `Swashbuckle.AspNetCore.Annotations` from 10.2.1 to 10.2.2 ([#325](#325)) ([317a97a](317a97a)) * bump `Swashbuckle.AspNetCore` from 10.2.1 to 10.2.2 ([#324](#324)) ([594d5dd](594d5dd)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stores optional warning/critical voltage thresholds per user and sensor so the client can color a voltage reading. Thresholds are unset by default — no coloring until the user configures them.
UserSensorVoltageThresholdentity (composite key UserId+SensorId), DbSet, and fluent config mirroringUserSensorCustomName, with an EF migration.PATCH/DELETE /sensors/{id}/voltage-thresholds, access-gated, validating that warning is above critical.WarningVoltage/CriticalVoltagemerged intoSensorDtoinGetAllSensors/GetSensorso the list carries them without an extra round-trip.