search timestamp handling about indigo HOT 2 CLOSED

time.go has

const ISO8601 = "2006-01-02T15:04:05.000Z"

will it always be at a higher time percision? In which case

const ISO8601 = "2006-01-02T15:04:05.000000Z" although i think it's no longer ISO8601 then, and i'm not sure what the format name is.

but it sounds like instead that it's back and forth, in which case

`func parseTimestamp(ts string) (time.Time, error) {
layouts := []string{
"2006-01-02T15:04:05.000Z",
"2006-01-02T15:04:05.000000Z",
// Add more layouts if necessary...
}

var parsedTime time.Time
var err error

for _, layout := range layouts {
    parsedTime, err = time.Parse(layout, ts)
    if err == nil {
        return parsedTime, nil
    }
}

return time.Time{}, fmt.Errorf("timestamp (%s) did not match any known layouts", ts)

}
`

should sort it out? Calling it in the indexPost func with

ts, err := parseTimestamp(rec.CreatedAt)

I can send a pr, but i'm not sure how exactly you want it to operate here.

from indigo.

it could also be that since i don't understand the requirements, that dropping digits as you suggested is actually the correct solution.

from indigo.