Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current documentation suggests that a calendar's hostname defaults to your server's hostname. This is not the case. If no domain is provided, ids are currently generated with an
@unspecified
suffix. This doesn't seem particularly useful or recommended, as appending@unspecified
won't help make ids unique.Appending a domain, while convenient and useful for a number of common uses, interferes other use cases. In my case, I want to be able to round-trip data from iCalendar format to JSON, so my inputs may already have domains present. Another use case is people who want to generated feeds with UUIDs.
This pull request adjusts the documentation to describe how you can construct feeds with either your server's hostname or with UUIDs, and adjusts the code and tests to treat calendar domains as optional.