Mike Danese 826f89d11d glide: add k8s deps 8 anos atrás
..
testdata 826f89d11d glide: add k8s deps 8 anos atrás
README.md 826f89d11d glide: add k8s deps 8 anos atrás
analytics.go 826f89d11d glide: add k8s deps 8 anos atrás
analytics_test.go 826f89d11d glide: add k8s deps 8 anos atrás
example_syncer.go 826f89d11d glide: add k8s deps 8 anos atrás
example_syncer_test.go 826f89d11d glide: add k8s deps 8 anos atrás
headers.go 826f89d11d glide: add k8s deps 8 anos atrás
headers_test.go 826f89d11d glide: add k8s deps 8 anos atrás
kubectl_dash_f.go 826f89d11d glide: add k8s deps 8 anos atrás
kubectl_dash_f_test.go 826f89d11d glide: add k8s deps 8 anos atrás
links.go 826f89d11d glide: add k8s deps 8 anos atrás
links_test.go 826f89d11d glide: add k8s deps 8 anos atrás
mungedocs.go 826f89d11d glide: add k8s deps 8 anos atrás
preformatted.go 826f89d11d glide: add k8s deps 8 anos atrás
preformatted_test.go 826f89d11d glide: add k8s deps 8 anos atrás
toc.go 826f89d11d glide: add k8s deps 8 anos atrás
toc_test.go 826f89d11d glide: add k8s deps 8 anos atrás
unversioned_warning.go 826f89d11d glide: add k8s deps 8 anos atrás
unversioned_warning_test.go 826f89d11d glide: add k8s deps 8 anos atrás
util.go 826f89d11d glide: add k8s deps 8 anos atrás
util_test.go 826f89d11d glide: add k8s deps 8 anos atrás
whitespace.go 826f89d11d glide: add k8s deps 8 anos atrás
whitespace_test.go 826f89d11d glide: add k8s deps 8 anos atrás

README.md

Documentation Mungers

Basically this is like lint/gofmt for md docs.

It basically does the following:

  • iterate over all files in the given doc root.
  • for each file split it into a slice (mungeLines) of lines (mungeLine)
  • a mungeline has metadata about each line typically determined by a 'fast' regex.
    • metadata contains things like 'is inside a preformmatted block'
    • contains a markdown header
    • has a link to another file
    • etc..
    • if you have a really slow regex with a lot of backtracking you might want to write a fast one to limit how often you run the slow one.
  • each munger is then called in turn
    • they are given the mungeLines
    • they create an entirely new set of mungeLines with their modifications
    • the new set is returned
  • the new set is then fed into the next munger.
  • in the end we might commit the end mungeLines to the file or not (--verify)

[Analytics]()