1.Remove repeat word 'with'

2.Update file writer example to README.md

3.Update fmt.Fprintln to buffer.WriteTo

Source code:

// addSeparator will write a new dash seperator line based on the args length
func (t *Tabby) addSeparator(args []interface{}) {
	var b bytes.Buffer
	/*...*/
	fmt.Fprintln(t.writer, b.String())
}

After changed:

// addSeparator will write a new dash seperator line based on the args length
func (t *Tabby) addSeparator(args []interface{}) {
	var b bytes.Buffer
	/*...*/
	b.WriteString("\n")
	b.WriteTo(t.writer)
}

Why did I make this change? I added benchmark test code of fmt.Fprintln and buffer.WriteTo in tabby_test.go, benchmark test code like this:

func BenchmarkBuffer(b *testing.B) {
    fd, _ := os.OpenFile("temp.txt", os.O_CREATE|os.O_TRUNC|os.O_WRONLY, 0644)
	defer fd.Close()
	b.ResetTimer()
	for i := 0; i < b.N; i++ {
		var buff bytes.Buffer
		buff.WriteString("TestString")
		buff.WriteString("\n")
		buff.WriteTo(fd)
	}
}

func BenchmarkFmt(b *testing.B) {
	fd, _ := os.OpenFile("temp.txt", os.O_CREATE|os.O_TRUNC|os.O_WRONLY, 0644)
	defer fd.Close()
	b.ResetTimer()
	for i := 0; i < b.N; i++ {
		var buff bytes.Buffer
		buff.WriteString("TestString")
		fmt.Fprintln(fd, buff.String())
	}
}

Run benchmark test command:

$ go test -run=NONE -bench="^Benchmark(Fmt|Buffer)$" -benchmem

And I get benchmark test data:

$ go test -run=NONE -bench="^Benchmark(Fmt|Buffer)$" -benchmem
goos: windows
goarch: amd64
pkg: tabby
BenchmarkBuffer-4         300000              4460 ns/op             112 B/op          1 allocs/op
BenchmarkFmt-4            300000              5103 ns/op             112 B/op          1 allocs/op
PASS
ok      tabby   3.470s

We can see buffer.WriteTo is more effective than fmt.Fprintln.

Hello,

I was just about to use your project, when I saw that it isn't licensed anywhere in writing. I the country I reside, that means I don't have a license and can't use it.

If this was intended to be an open source / freely available, I would recommend putting a license within the project.

Thanks, -Daniel

AddLine accepts a variadic []interface{}. Because of this, using t.AddLine(slice...) where slice is a []string does not work.

Propose new method "AddLineS(args []string...)."

Simple fmt.Println doesn't work really. It prints the newlines before all of the tables:

package main

import (
	"github.com/cheynewallace/tabby"
	"fmt"
)

func main() {
	t := tabby.New()
	t.AddHeader("Lice", "Präsens", "Präteritum", "Prät. Konjunktiv", "Imperativ")
	t.AddLine("Ich", "bin", "war", "wäre", "-")
	t.AddLine("Du", "bist", "warst", "wärest", "-")
	t.AddLine("Er", "ist", "war", "wäre", "-")
	fmt.Println("\n")
	t.AddHeader("Infinitiv", "Präteritum", "Partizip II")
	t.AddLine("sein", "war", "ist gewesen")

	t.Print()
}

You get this:

Lice       Präsens      Präteritum   Prät. Konjunktiv   Imperativ
----       --------     -----------  -----------------  ---------
Ich        bin          war          wäre               -
Du         bist         warst        wärest             -
Er         ist          war          wäre               -
Infinitiv  Präteritum   Partizip II
---------  -----------  -----------
sein       war          ist gewesen

Strings in Japanese are not aligned, you might to use utf8.RuneCountInString instead of len to compute the length of the strings.

Example

• https://go.dev/play/p/CUsKLViOtlR

Output

COMPANY          CITY  ISSUE
-------          ----  -----
AAAホールディングス株式会社  東京    〇についての問い合わせ
トトト株式会社          名古屋   〇〇できない
桜株式会社            大阪    〇の不具合

Asking if you could add colored output per column and row. Alternatively, if someone knows of a golang package to use to print colored columns let me know.

AddHeader declares the table header does not necessarily add, the example below explains better my point of view

package main

import "github.com/cheynewallace/tabby"

func main(){
	t := tabby.New()
	t.AddHeader("NAME", "TITLE", "DEPARTMENT")
	t.AddLine("John Smith", "Developer", "Engineering")
	t.AddHeader("NAME", "TITLE", "DEPARTMENT")
	t.Print()
}

OUT:

NAME        TITLE      DEPARTMENT
----        -----      ----------
John Smith  Developer  Engineering

SetHeader sounds better