Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Set a DTSTAMP for new VEVENT/VTODO components #193

Closed
WhyNotHugo opened this issue Apr 17, 2016 · 2 comments
Closed

Set a DTSTAMP for new VEVENT/VTODO components #193

WhyNotHugo opened this issue Apr 17, 2016 · 2 comments

Comments

@WhyNotHugo
Copy link
Contributor

VTODO (amongst others) components MUST a DTSTAMP entry, and it should contain the timestamp of the components creation.

I'd like to propose that creating new components of these types have this value automatically added, with datetime.now as a default.

This will basically make these components standards-compliant (and the value is an expected one too).

@geier
Copy link
Collaborator

geier commented Apr 18, 2016

icalendar's current approach is to let the user handle everything themselves. Convenience functions, like the one suggested here, could go hand in hand with implementing a validation checker (as mentioned in #28). This could be a point for the 4.0 roadmap (#186) if anyone is interested in working on it.

@untitaker
Copy link
Contributor

My position is that icalendar really shouldn't let the user produce invalid data by default. A validation checker is opt-in.

@collective collective locked and limited conversation to collaborators Aug 30, 2023
@niccokunzmann niccokunzmann converted this issue into discussion #542 Aug 30, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants