aarondandy / wharrgarbl Goto Github PK

• build scripts
• nuget packages
• dogfood

• Append(string)
• String extensions like .ToDirectoryInfo
• methods should take multiple relative parameters: `folder1.File("folder2","fileName.ext")
• a method like SubDir could take an extra parameter, like bool create
• In addition to EnumerateFiles there could be EnumerateFileNames
• Creating or deleting a directory/file sometimes requires waiting
  • Could be nice to have a special overload on DirectoryInfo/DirectoryPath for example to allow for a max wait time, or polling to see if the dead is done
  • A .Delete that does not throw would be good
  • folders.ForEach(d => d.Delete(wait: false)); folders.WaitAll(d => !d.Exists); or something equally horrible could be handy. folders.DeleteAll(recursive: true) could be better though
• A copy method for paths could be neat, instead of File.Copy(a,b) it could be a.CopyTo(b)

Some kind of static method wrapper to allow use of var with a lambda (maybe some other trick?)

var doIt = _f(int a,string b => "meh");

and I think I have seen this before somewhere...

• Concat single item: .Concat(x) vs .Concat(new[]{x})
• easily create collections, even when the parameter may be null MakeList(stuff) vs new List<T>(stuff ?? Enumerable.Empty<T>())
• ForEach without needing it to be a list, foreach(var thing in stuff) doIt(thing); vs stuff.ForEach(thing => doIt(thing)); or even stuff.ForEach(doIt);
  • Just a void version of select
• Conditional concat: new[] { "unit", "component" }.ConcatIf(string.IsNullOrWhiteSpace(ci), "accept").Concat("pack")
  • ConcatIf could have a Func version as well
  • string.IsNullOrWhiteSpace(ci) ? new[] { "unit", "component", "pack" } : new[] { "unit", "component", "accept", "pack" } can be less redundant
• WhereNot

Create a shorter version of (T)Enum.Parse(typeof(T), text, true) also a nullable variant.

Some anonymous/dynamic type helpers could be handy

• String.Join(",",stuff) or stuff.Join(",")

• parse version numbers from assembly info files
• read version numbers from assemblies

With new versions of scriptcs and roslyn the static using syntax has changed. All types with "functions" must have their usings changed.

• DirectoryInfo and FileInfo abstractions to make working with paths easier.
  • Implicit conversions to string and from string could be handy.
  • typed operator + would be good, can't add two files but can add directory + file or directory + string
  • var artifactDir = buildDir.Parent.SubDir("artifacts");
  • SubDir and File methods should take multiple parameters: folder1.File("folder2","fileName.ext")
  • a method like SubDir could take an extra parameter, like bool create
  • fileInfos.Select(f => f.FullName) could be filePaths.Cast<string>()
  • In addition to EnumerateFiles there could be EnumerateFileNames
• Creating or deleting a directory/file sometimes requires waiting
  • Could be nice to have a special overload on DirectoryInfo/DirectoryPath for example to allow for a max wait time, or polling to see if the dead is done
  • A .Delete that does not throw would be good
  • folders.ForEach(d => d.Delete(wait: false)); folders.WaitAll(d => !d.Exists); or something equally horrible could be handy. folders.DeleteAll(recursive: true) could be better though
• A copy method for paths could be neat, instead of File.Copy(a,b) it could be a.CopyTo(b)
• String extensions like .ToDirectoryPath

Glob searches for paths using multiple ** and * and other things like ?