refactor(Tarifeinschraenkung): reference Zaehlertyp instead of Geraet - #1140
Open
lord-haffi wants to merge 1 commit into
Open
refactor(Tarifeinschraenkung): reference Zaehlertyp instead of Geraet#1140lord-haffi wants to merge 1 commit into
Zaehlertyp instead of Geraet#1140lord-haffi wants to merge 1 commit into
Conversation
Die Einschränkung betrifft die Art des Zählers, nicht ein konkretes Gerät. Closes #1136
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.
Ändert
COM Tarifeinschraenkung.einschraenkungzaehlervonlist[Geraet]auflist[Zaehlertyp](Workshop-Beschluss 2026-05-06/07).Die Einschränkung betrifft die Art des Zählers, nicht ein konkretes Gerät; ein
BO Geraetmit Gerätenummer war hier zu spezifisch.Breaking change: der Feldtyp wechselt von BO-Referenz auf Enum-Wert.
Hinweis: berührt dieselbe Klasse wie #1139 (angrenzende Zeilen), ggf. trivialer Merge-Konflikt je nach Merge-Reihenfolge.
Verifiziert:
pytest107 passed,ruff check src/bo4eclean,mypy src/bo4eclean, JSON-Schema-Generierung ok.Closes #1136