6 Commits (13ea97a1dfebf0980d45bbdc1a2148ae341b9840)

Author	SHA1	Message	Date
Adrien Delorme	819329228a	Change back to make sure all durations are a time.Duration ... It is simply the best/simplest solution and trying to prevent users from passing and integer here would be like opening a can of worms. Because: * we cannot make mapstructure validate our duration string ( with an UnmarshalJSON func etc.) * we cannot make mapstructure spit a string instead of a duration and packer will decode-encode-decode config. * the hcl2 generated code asks for a string, so this will be enforced by default.	6 years ago
Adrien Delorme	bf3d9841c6	Force durations to be passed a strings ... Before this commit it was possible to set a duration using an integer or a float. Go's time.Duration is an int64 internally an mapstructure will take advantage of this and load the number as a int64 but `1` means one ns which is unexpected/confusing. To avoid confusion and enforce readability this forces users to pass a string with a unit for a duration; ex "56s".	6 years ago
Adrien Delorme	0fe48691e8	ignore doc fields containing `TODO`	7 years ago
Adrien Delorme	ec52f36af1	docs: escape pointer (*) parameters `*` => `\*` ... so that we don't get weird italics there and there	7 years ago
Adrien Delorme	349c3ef74b	cmd/struct-markdown: also generate docs from header comments of a struct ... & generate it for ISOConfig	7 years ago
Adrien Delorme	4ae10f08b2	docs: generate builders partials from struct comments	7 years ago