Skip to content

[tw-caldav] Fix no priority RFC complaince#156

Open
ferdinandyb wants to merge 1 commit into
bergercookie:masterfrom
ferdinandyb:master
Open

[tw-caldav] Fix no priority RFC complaince#156
ferdinandyb wants to merge 1 commit into
bergercookie:masterfrom
ferdinandyb:master

Conversation

@ferdinandyb

@ferdinandyb ferdinandyb commented Oct 24, 2025

Copy link
Copy Markdown

Description

According to the RFC, the correct value for an undefined priority is 0, not an empty string. The caldav package definitely chokes on non-int priorities making it to server-side, when trying to download them.

Link: https://datatracker.ietf.org/doc/html/rfc5545#section-3.8.1.9

Fixes # (issue)

Type of change

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Please also list any relevant details for your
test configuration

  • I checked in nextcloud and the Tasks android app that indeed "no priority" is priority=0, so at least these two applications take the RFC seriously
  • I enable checking priority for caldav items, so now the test will fail if the priority is not 0 or one of the mapped numbers

Checklist

N/A is striked through

  • My code follows the style guidelines of this project
    - [ ] I have commented my code, particularly in hard-to-understand areas
    - [ ] I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
    - [ ] Any dependent changes have been merged and published in downstream modules

According to the RFC, the correct value for an undefined priority is 0,
not an empty string. The `caldav` package definitely chokes on non-int
priorities making it to server-side, when trying to download them.

Link: https://datatracker.ietf.org/doc/html/rfc5545#section-3.8.1.9
@shymega

shymega commented Jun 27, 2026

Copy link
Copy Markdown
Collaborator

I'm mostly happy with this, but could you move the PR description to the 'Description' section please?

Then we can merge.

@ferdinandyb

Copy link
Copy Markdown
Author

I'm mostly happy with this, but could you move the PR description to the 'Description' section please?

Then we can merge.

done, thank!

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.

2 participants