workarounds for bad go comment formatting behavior

evanw · Aug 2, 2022 · 296870e · 296870e
1 parent af0ab3e
commit 296870e
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/internal/fs/filepath.go b/internal/fs/filepath.go
@@ -359,8 +359,8 @@ func (fp goFilepath) fromSlash(path string) string {
 // If the result of this process is an empty string, Clean
 // returns the string ".".
 //
-// See also Rob Pike, “Lexical File Names in Plan 9 or
-// Getting Dot-Dot Right,”
+// See also Rob Pike, "Lexical File Names in Plan 9 or
+// Getting Dot-Dot Right,"
 // https://9p.io/sys/doc/lexnames.html
 func (fp goFilepath) clean(path string) string {
 	originalPath := path

diff --git a/internal/resolver/resolver.go b/internal/resolver/resolver.go
@@ -1179,9 +1179,9 @@ func (r resolverQuery) dirInfoUncached(path string) *dirInfo {
 	return info
 }
 
-// https://devblogs.microsoft.com/typescript/announcing-typescript-4-7-beta/#resolution-customization-with-modulesuffixes
-// "Note that the empty string ” in moduleSuffixes is necessary for TypeScript to
-// also look-up ./foo.ts. In a sense, the default value for moduleSuffixes is [”]."
+// From: https://devblogs.microsoft.com/typescript/announcing-typescript-4-7-beta/#resolution-customization-with-modulesuffixes
+// Note that the empty string "" in moduleSuffixes is necessary for TypeScript to
+// also look-up ./foo.ts. In a sense, the default value for moduleSuffixes is [""].
 var defaultModuleSuffixes = []string{""}
 
 var rewrittenFileExtensions = map[string][]string{