Enhancement: Channel number inputs in stream-to-channel creation modals no longer have a maximum value restriction, allowing users to enter any valid channel number supported by the database

This commit is contained in:
SergeantPanda 2025-12-26 15:55:25 -06:00
parent bc3ef1a3a9
commit 1b1f360705
2 changed files with 1 additions and 2 deletions

View file

@ -21,6 +21,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
### Changed
- Fixed event viewer arrow direction (previously inverted) — UI behavior corrected. - Thanks [@drnikcuk](https://github.com/drnikcuk) (Closes #772)
- Channel number inputs in stream-to-channel creation modals no longer have a maximum value restriction, allowing users to enter any valid channel number supported by the database
- Stream log parsing refactored to use factory pattern: Simplified `ChannelService.parse_and_store_stream_info()` to route parsing through specialized log parsers instead of inline program-specific logic (~150 lines of code removed)
- Stream profile names in fixtures updated to use proper capitalization (ffmpeg → FFmpeg, streamlink → Streamlink)

View file

@ -1157,7 +1157,6 @@ const StreamsTable = () => {
value={customStartNumber}
onChange={setCustomStartNumber}
min={1}
max={9999}
placeholder="Enter starting number..."
/>
)}
@ -1227,7 +1226,6 @@ const StreamsTable = () => {
value={specificChannelNumber}
onChange={setSpecificChannelNumber}
min={1}
max={9999}
placeholder="Enter channel number..."
/>
)}