{"id":36392,"date":"2022-06-30T14:37:33","date_gmt":"2022-06-30T18:37:33","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=36392"},"modified":"2022-06-30T14:37:33","modified_gmt":"2022-06-30T18:37:33","slug":"swift-url-improvements-at-wwdc-2022","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/06\/30\/swift-url-improvements-at-wwdc-2022\/","title":{"rendered":"Swift URL Improvements at WWDC 2022"},"content":{"rendered":"

Natalia Panferova<\/a> (tweet<\/a>):<\/p>\n

\n

Previously, to obtain the path to a file in the application folder, we had to use FileManager<\/code> APIs, which are quite cumbersome. Now, we can get the paths to system folders directly from static properties on URL<\/code> type.<\/p>\n<\/blockquote>\n

However, it sounds like the new API—which does not throw any errors—does not guarantee that the folder actually exists.<\/p>\n\n

Another great improvement is the new appending(path:directoryHint:)<\/a> method, that replaces the old appendingPathComponent(_:isDirectory:)<\/a>. The new method accepts a DirectoryHint<\/a> parameter, which indicates whether Foundation should perform a file system check to determine if the path refers to a folder. The default value is inferFromPath<\/a>, meaning that this information will be inferred from the path string we pass to the method. If the string contains a trailing slash, it will be treated as a directory path.<\/p><\/blockquote>\n

That deserves a “finally,” because for 20+ years most code (which omits the isDirectory<\/code> parameter) has been incurring overhead for accessing the file system every time a URL is created.<\/p>\n\n

Previously:<\/p>\n