-
-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prefix mailto: for email in organizer property #88
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Agreed. Consistency is king, also the spec is very clear on this too: https://www.kanzaki.com/docs/ical/calAddress.html I'm not sure if it can be something else. This might break some existing deployments. I will get back to this, in a couple days. |
Need to delay, interview prep. |
I don't know if this is "clean", but if you have concerns about the user sending in email with "mailto:" prefix, I think we can probably consider only conditionally adding it by checking the prefix. |
It makes sense and if there is an issue someone can submit an issue and we can add a new code path. There is almost no need for duplication. |
Sounds good, I've updated it to only conditionally add it. Also updated the attendee one to be similar. Let me know if I should revert how attendee works to previous version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mailto:
is capitalized in the rfc might as well stick to that too. -- If there is a string const use that?
But other than that looks good. |
Spent a bit more time looking into the spec. Looks like it is possible to have prefixes other than "mailto:" here. A CAL-ADDRESS can be a URI and if you see the doc, a URI can be more than just mailto. I think it might be incorrect to automatically add
I see the examples in the RFC to be using lowercase. I also see that there has been a previous discussion about this here.
There is none defined as of now, but I can add one if we are certain about adding the |
haha yep. I'm in a loop. Okay. Nothing more is necessary. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks for looking that up. I have a shocking memory it seems. There you go: |
Organizer property should be similar to how attendee is handled.
golang-ical/components.go
Lines 260 to 262 in 0fcebed