{"id":440,"date":"2021-04-03T18:58:14","date_gmt":"2021-04-03T16:58:14","guid":{"rendered":"https:\/\/mic.st\/blog\/?p=440"},"modified":"2021-04-03T18:58:16","modified_gmt":"2021-04-03T16:58:16","slug":"how-to-use-the-relativedatetimeformatter-in-swift","status":"publish","type":"post","link":"https:\/\/mic.st\/blog\/how-to-use-the-relativedatetimeformatter-in-swift\/","title":{"rendered":"How to use the RelativeDateTimeFormatter in Swift"},"content":{"rendered":"\n

Working with dates in Swift is a thing I remembered to struggle for a long time as a Junior developer. However, you should get used to objects that have date properties. E.g. you can sort stuff (e.g. see https:\/\/mic.st\/blog\/how-to-sort-an-array-of-objects-by-date-property\/<\/a>) easily by date. If you ever tried to develop your own date formatter, you will quickly run into a lot of pitfalls (Even before talking about localization\ud83d\ude04). Here, I will give you an overview on how to use the RelativeDateTimeFormatter<\/strong> in Swift.<\/p>\n\n\n\n

Currently, I am working on a private project that includes local notifications and a small dashboard that shows short information about these notifications. I wanted to make it friendly with something like “next notification in 18 hours”, etc.
So, how would you do that?
My first solution was to just present the notification’s trigger Date<\/code> using the powerful and well known DateFormatter<\/code> or DateComponentsFormatter<\/code> plus some logic.
This is totally fine and might work. However, there is also a nice formatter for just this single use case. \ud83e\udd73
Furthermore, one of the things I have learnt so far using Swift: If it’s already built-in, do not reeinvent it because your solution is most probably worse (especially when localization is involved \ud83d\ude04)<\/strong>
<\/p>\n\n\n\n

\"An
Formatting times in Swift can look as nice as this stock photo!<\/figcaption><\/figure><\/div>\n\n\n\n

(I am not sure why Apple did not mention this nice formatter in the Date and Times overview at https:\/\/developer.apple.com\/documentation\/foundation\/dates_and_times<\/a>. However, it is mentioned on the general overview with all the formatters: https:\/\/developer.apple.com\/documentation\/foundation\/data_formatting <\/a>)<\/p>\n\n\n\n

The formatter’s output<\/h2>\n\n\n\n

The documentation in the Obj-C header states pretty clear what you can expect from this formatter. It will give you a “local-aware formatting of a relative date or time”. E.g. something like I want to have for my notifcations: “Next: In two weeks”<\/em>. You pass in two dates (one is your reference dates) and it calculates the difference and produces a nice string for you.<\/p>\n\n\n\n

Although you can technically concatenate your formatter’s results to an existing string, you have to make sure that this will not conflict in a grammatical sense. <\/p>\n\n\n\n

The code documentation also says that you should use the formatter’s results only “in a standalone manner”. <\/p>\n\n\n\n

Using the formatter<\/h2>\n\n\n\n

There are four available methods that allow you to format time in different representations to a string:<\/p>\n\n\n

func localizedString(for<\/span>: Date<\/span>, relativeTo<\/span>: Date<\/span>) -> String<\/span>\nfunc localizedString(from<\/span>: DateComponents) -> String<\/span>\nfunc localizedString(fromTimeInterval: TimeInterval) -> String<\/span>\nfunc string(for<\/span>: Any?) -> String<\/span>?<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
The one you would use most commonly, might be localizedString(for: Date, relativeTo: Date)<\/code>. Imagine, someone is standing at a certain point in time (your second parameter) reasoning about another date (which is your first parameter). That means, your second parameter is in most cases Date()<\/code>.<\/p>\n\n\n\n
What is really cool about the formatter is that it not only handles plurals for you, it also aproximates really nice. So, it does not just format a date that is ten days in the past to “10 days ago”<\/em>, it will actually format everything that makes sense to “last week”<\/em>, “next week”<\/em>, etc.<\/p>\n\n\n\n
Let’s see an easy example of the formatter in action:<\/p>\n\n\n
let<\/span> formatter = RelativeDateTimeFormatter<\/span>()\nlet<\/span> calendar = Calendar<\/span>.current\nlet<\/span> today = Date<\/span>()\n\n\/\/ Some other points in time. <\/span>\nif<\/span> let<\/span> lastWeek = calendar.date(byAdding: DateComponents<\/span>(day: -10<\/span>),\n\t\t\t\t\t\t\t\tto: Date<\/span>()),\n   let<\/span> lastWeekAsWell = calendar.date(byAdding: DateComponents<\/span>(day: -8<\/span>),\n\t\t\t\t\t\t\t\tto: Date<\/span>()),\n   let<\/span> twoWeeksAgo = calendar.date(byAdding: DateComponents<\/span>(day: -18<\/span>),\n\t\t\t\t\t\t\t\t   to: Date<\/span>()),\n   let<\/span> lastMonth = calendar.date(byAdding: DateComponents<\/span>(day: -40<\/span>),\n\t\t\t\t\t\t\t\t to: Date<\/span>()) {\n   let<\/span> nextYear = calendar.date(byAdding: DateComponents<\/span>(month: 16<\/span>),\n\t\t\t\t\t\t\t\tto: today)\n\tformatter.localizedString(for<\/span>: lastWeek, relativeTo: today)\n\tformatter.localizedString(for<\/span>: lastWeekAsWell, relativeTo: today)\n\tformatter.localizedString(for<\/span>: twoWeeksAgo, relativeTo: today)\n\tformatter.localizedString(for<\/span>: lastMonth, relativeTo: today)\n\tformatter.localizedString(for<\/span>: nextYear, relativeTo: today)\n\n\t\/\/\tPrints:<\/span>\n\t\/\/\t\"1 week ago\"<\/span>\n\t\/\/\t\"1 week ago\"<\/span>\n\t\/\/\t\"2 weeks ago\"<\/span>\n\t\/\/\t\"1 month ago\"<\/span>\n\t\/\/\t\"in 1 year\"<\/span>\n}<\/code><\/span>Code language:<\/span> Swift<\/span> (<\/span>swift<\/span>)<\/span><\/small><\/pre>\n\n\n
As you can see above, the formatter approximates eight days in the past and ten days in the past to “1 week ago”<\/em> which is pretty cool, right?<\/p>\n\n\n\n
Shorthand method for the RelativeDateTimeFormatter<\/h2>\n\n\n\n
There is another method that is inherited from Formatter<\/code> which accepts Any<\/code> (func string(for: Any?) -> String?<\/code>) However, it will only return something else than nil<\/code> if you pass in a Date<\/code>. It uses Date()<\/code> as reference date, therefore you can use it as a shorthand for the first presented method. It will give you the same result:<\/p>\n\n\n
formatter.string(for<\/span>: lastWeek)\nformatter.string(for<\/span>: lastWeekAsWell)\nformatter.string(for<\/span>: twoWeeksAgo)\nformatter.string(for<\/span>: lastMonth)\nformatter.string(for<\/span>: nextYear)\n\n\/\/\tPrints the same as above, given the properties above hold the same values<\/span>\n\/\/\t\"1 week ago\"<\/span>\n\/\/\t\"1 week ago\"<\/span>\n\/\/\t\"2 weeks ago\"<\/span>\n\/\/\t\"1 month ago\"<\/span>\n\/\/\t\"in 1 year\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
What if you want the exact amount of days, weeks, years or whatever? You can use func localizedString(from: DateComponents)<\/code> for that. It will use Date()<\/code> as a default reference and the formatter does not approximate anything (like we saw before). If you use the same quantities we added above to today<\/code> you will get the exact amounts in your string:<\/p>\n\n\n
formatter.localizedString(from<\/span>: DateComponents(day: -10<\/span>))\nformatter.localizedString(from<\/span>: DateComponents(day: -8<\/span>))\nformatter.localizedString(from<\/span>: DateComponents(day: -18<\/span>))\nformatter.localizedString(from<\/span>: DateComponents(day: -40<\/span>))\nformatter.localizedString(from<\/span>: DateComponents(month: 16<\/span>))\n\n\/\/\tPrints:<\/span>\n\/\/\t\"10 days ago\"<\/span>\n\/\/\t\"8 days ago\"<\/span>\n\/\/\t\"18 days ago\"<\/span>\n\/\/\t\"40 days ago\"<\/span>\n\/\/\t\"in 16 months\"<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
The third method localizedString(fromTimeInterval: TimeInterval)<\/code> is a convenience method for creating a string from a TimeInterval<\/code>. It behaves like the method for creating a string from DateComponents<\/code>. However, for longer timespans I recommend not to use it. DateComponents(day: 5)<\/code> reads way better than 60 * 60 * 24 * 5<\/code>. In addition to that, you will loose accuracy when using TimeInterval<\/code> for longer periods.<\/p>\n\n\n\n
The fourth method is inherited from Formatter<\/code> that is why you can pass in Any<\/code>. However, it will only return something else than nil<\/code> if you pass in a Date<\/code>. It uses Date()<\/code> as reference date, therefore you can use it as a shorthand for the first presented method:<\/p>\n\n\n\n
Now that we learnt something about the different methods, let’s see how we can configure the formatter.<\/p>\n\n\n\n
Configuring the RelativeDateTimeFormatter<\/h2>\n\n\n\n
You should have now an understanding about how to use the RelativeDateTimeFormatter in Swift. So, it does a pretty great job without configuring anything. Actually, this formatter does not offer a lot of configuring properties but I think it is sufficient in most cases. <\/p>\n\n\n\n
In the following listing you can see all the available properties with some documentation by me. You should be familar with some of them if you already worked with DateFormatter<\/code>:<\/p>\n\n\n
\/\/\/ You can set this property to .named or .numeric.<\/span>\n<\/span><\/span>\/\/\/ .numeric will give you \"1 day ago\", \"1 week ago\", etc.<\/span>\n<\/span><\/span>\/\/\/ .named will give you \"yesterday\", \"last week\", etc.<\/span>\n<\/span><\/span>var<\/span> dateTimeStyle: RelativeDateTimeFormatter<\/span>.DateTimeStyle<\/span>\n<\/span><\/span>\n<\/span><\/span>\n<\/span><\/span>\/\/\/ Use this to modify how the units and quantaties are formatted.<\/span>\n<\/span><\/span>\/\/\/ E.g. for a date that is 2 days in the past:<\/span>\n<\/span><\/span>\/\/\/ .full will result in \"2 days ago\"<\/span>\n<\/span><\/span>\/\/\/ .abbreviated will result in \"2 d. ago\"<\/span>\n<\/span><\/span>var<\/span> unitsStyle: RelativeDateTimeFormatter<\/span>.UnitsStyle<\/span>\n<\/span><\/span>\n<\/span><\/span>\/\/\/ This sets where the formatted string will be used to format correctly.<\/span>\n<\/span><\/span>\/\/\/ E.g. in a lot of languages the first letter of a sentence is capatalized.<\/span>\n<\/span><\/span>\/\/\/ You can just use .beginningOfSentence  for that.<\/span>\n<\/span><\/span>\/\/\/ In other cases you might use .<\/span>\n<\/span><\/span>var<\/span> formattingContext: Formatter<\/span>.Context<\/span>\n<\/span><\/span><\/code><\/span>Code language:<\/span> Swift<\/span> (<\/span>swift<\/span>)<\/span><\/small><\/pre>\n\n\n
There are two other ones you probably will not need to change because you should respect whatever the users have set on their devices: <\/p>\n\n\n
\/\/\/ The calendar used by the formatter.<\/span>\n\/\/\/ E.g. .chinese, .gregorian, .hebrew and a lot more.<\/span>\n\/\/\/ Normally you do not have to set this.<\/span>\n\/\/\/ You should let the system apply whatever users picked on their phone.<\/span>\n\/\/\/ Defaults to Calendar.autoupdatingCalendar.<\/span>\nvar<\/span> calendar: Calendar!\n\n\/\/\/ Similar to calendar, normally you do not need to set this.<\/span>\n\/\/\/ By default, the calendar's locale is used here.<\/span>\nvar<\/span> locale: Locale!<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
More complex time formatting<\/h2>\n\n\n\n
This post should have given you a short introduction into how to use the RelativeDateTimeFormatter in Swift. However, there are cases where this formatter might not be enough. If you want to format dates that should be placed in a text or need more complex formatting behavior in general, I would rather use DateComponentsFormatter<\/code> together with NSLocalizedString<\/code>. If you use RelativeDateTimeFormatter<\/code> in non-standalone places you might end up with funny looking texts. You should be aware that it might look totally fine in your preferred language but it might not work in other languages.<\/p>\n\n\n\n
Happy time formatting! \u23f0<\/p>\n","protected":false},"excerpt":{"rendered":"
Working with dates in Swift is a thing I remembered to struggle for a long time as a Junior developer. However, you should get used to objects that have date properties. E.g. you can sort stuff (e.g. see https:\/\/mic.st\/blog\/how-to-sort-an-array-of-objects-by-date-property\/) easily by date. If you ever tried to develop your own date formatter, you will quickly…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[3],"tags":[41,4,35],"class_list":["post-440","post","type-post","status-publish","format-standard","hentry","category-ios-development","tag-formatters","tag-ios","tag-swift"],"_links":{"self":[{"href":"https:\/\/mic.st\/blog\/wp-json\/wp\/v2\/posts\/440","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mic.st\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mic.st\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mic.st\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mic.st\/blog\/wp-json\/wp\/v2\/comments?post=440"}],"version-history":[{"count":26,"href":"https:\/\/mic.st\/blog\/wp-json\/wp\/v2\/posts\/440\/revisions"}],"predecessor-version":[{"id":471,"href":"https:\/\/mic.st\/blog\/wp-json\/wp\/v2\/posts\/440\/revisions\/471"}],"wp:attachment":[{"href":"https:\/\/mic.st\/blog\/wp-json\/wp\/v2\/media?parent=440"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mic.st\/blog\/wp-json\/wp\/v2\/categories?post=440"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mic.st\/blog\/wp-json\/wp\/v2\/tags?post=440"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}