From 8e1bce1d0669b76de131dfe2b56f771ab527ea5c Mon Sep 17 00:00:00 2001 From: Matt Nadareski Date: Fri, 24 Feb 2017 12:08:33 -0800 Subject: [PATCH] [DatFile] Remove TODOs --- SabreTools.Helper/Dats/Partials/DatFile.Parsers.cs | 7 ------- SabreTools.Helper/Dats/Partials/DatFile.Writers.cs | 1 - 2 files changed, 8 deletions(-) diff --git a/SabreTools.Helper/Dats/Partials/DatFile.Parsers.cs b/SabreTools.Helper/Dats/Partials/DatFile.Parsers.cs index 5b9a567f..b67eb619 100644 --- a/SabreTools.Helper/Dats/Partials/DatFile.Parsers.cs +++ b/SabreTools.Helper/Dats/Partials/DatFile.Parsers.cs @@ -59,13 +59,6 @@ namespace SabreTools.Helper.Dats /// True if descriptions should be used as names, false otherwise (default) /// True if original extension should be kept, false otherwise (default) /// True if tags from the DAT should be used to merge the output, false otherwise (default) - /// - /// TODO: Add CSV and TSV parsing. - /// Can they be in the same parser? All it would technically need is the delimiter that it should be looking - /// for and it would be able to read them individually. Also, take into account different types of formats, - /// possibly by looking at the first line headings, determining what columns those correspond to, and then - /// keeping track of what goes to what in the map. That would allow for a VERY flexible reading of inputs. - /// public void Parse( // Standard Dat parsing string filename, diff --git a/SabreTools.Helper/Dats/Partials/DatFile.Writers.cs b/SabreTools.Helper/Dats/Partials/DatFile.Writers.cs index 21d8e0d2..687662be 100644 --- a/SabreTools.Helper/Dats/Partials/DatFile.Writers.cs +++ b/SabreTools.Helper/Dats/Partials/DatFile.Writers.cs @@ -999,7 +999,6 @@ namespace SabreTools.Helper.Dats RepExt = ""; } - // TODO: Find out why this code strips out partial paths string dir = Path.GetDirectoryName(name); dir = (dir.StartsWith(Path.DirectorySeparatorChar.ToString()) ? dir.Remove(0, 1) : dir); name = Path.Combine(dir, Path.GetFileNameWithoutExtension(name) + RepExt);