Skip to content

fix(proposals): handle invalid timezone fallback - #8931

Closed
Kumar-s75 wants to merge 1 commit into
nextcloud:mainfrom
Kumar-s75:fix/proposal-timezone-logger
Closed

Kumar-s75 wants to merge 1 commit into
nextcloud:mainfrom
Kumar-s75:fix/proposal-timezone-logger

Conversation

@Kumar-s75

Copy link
Copy Markdown
Contributor

Summary

  • import the Calendar logger used by the timezone-offset fallback
  • add a regression test for invalid timezone identifiers
  • preserve the intended UTC offset fallback instead of throwing a ReferenceError

Tests

  • npm run test:unit -- tests/javascript/unit/services/timezoneOffsetService.test.ts --reporter=dot
  • TZ=UTC npm run test:unit -- --reporter=dot (519 tests passed)
  • npx eslint src/services/timezoneOffsetService.ts tests/javascript/unit/services/timezoneOffsetService.test.ts

Closes #8928

Import the logger used by the timezone offset error path and cover the UTC fallback with a regression test.

Fixes nextcloud#8928

Signed-off-by: Kumar Saurabh <kumarsaurabh27d@gmail.com>
@Kumar-s75
Kumar-s75 force-pushed the fix/proposal-timezone-logger branch from 3c466de to b72b7bf Compare September 12, 2026 11:21
@odzhychko

Copy link
Copy Markdown
Contributor

Duplicate of #8917

@odzhychko odzhychko marked this as a duplicate of #8917 Sep 14, 2026
@odzhychko odzhychko closed this Sep 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Invalid meeting proposal timezone causes ReferenceError in offset fallback

2 participants