A method to format DateComponents with units style.
A method to parse String using ISO8601DateFormatter.
Removed
Date.date() constructor methods.
Duration.
Time zone support for each Date.
Properties to get beginning and end of periods such as beginningOfYear, endOfMonth.
change().
Updated
For Int, year, month and so on creates new DateComponents instance instead of Duration.
Background thought
In my poor English, I describe the reasons for these changes here.
I work on an iOS project at my office on weekdays and I enjoy with my wife on weekends (I have married at last July). So, I don't have enough time to work on OSS activities.
At August 2014, I have started this experimental project just to learn about Swift. Fortunately, a lot of stars, issues and pull requests came to here. It was surprising for me and encouraged me as an iOS programmer. But, at the same time, I felt sorry about issues and pull requests that I didn't have enough time to take on. More features this library has, More maintenance cost I have to pay. I knew there are similar libraries that has rich features.
Then, I decided to keep this library small and correct. Small library doesn't have rich features but is easier to maintain and to look over the inside. If it is too simple to help you, you should select another rich library or build library by yourself.
Added
Date.+and-betweenDateComponentsDatewith date style.DateComponentswith units style.StringusingISO8601DateFormatter.Removed
Date.date()constructor methods.Duration.Date.beginningOfYear,endOfMonth.change().Updated
Int,year,monthand so on creates newDateComponentsinstance instead ofDuration.Background thought
In my poor English, I describe the reasons for these changes here.
I work on an iOS project at my office on weekdays and I enjoy with my wife on weekends (I have married at last July). So, I don't have enough time to work on OSS activities.
At August 2014, I have started this experimental project just to learn about Swift. Fortunately, a lot of stars, issues and pull requests came to here. It was surprising for me and encouraged me as an iOS programmer. But, at the same time, I felt sorry about issues and pull requests that I didn't have enough time to take on. More features this library has, More maintenance cost I have to pay. I knew there are similar libraries that has rich features.
Then, I decided to keep this library small and correct. Small library doesn't have rich features but is easier to maintain and to look over the inside. If it is too simple to help you, you should select another rich library or build library by yourself.