Thad Guidry

I second @tfmorris opinion. I like the consistency of when our API standards have a context that could be "one or many" then we resort to Array form. (mostly because...

@acka47 If we went that route, we'd have to adopt a convention and document it. That being the key should be an ISO 639-3 three letter code? Hmm, what else?

>OpenRefine includes a type= query parameter to its auto-completion HTTP calls for properties, letting the reconciliation service to suggest properties which are relevant for the given type. Sorry, the wording...

> I feel like something is missing from @thadguidry's response? clarified by adding my question to @wetneb directly on the RESPONSE

The quotes around "spec" that @tfmorris used is a way Americans sometimes say softly or loosely or unreal. So, soft "spec" or loose "spec". He wasn't saying real spec. Which...

@bear Hmm. OK. Makes sense. I was hoping for some kind of way now for parsedatetime to return to me a level of confidence that it has a Day, Month,...

Doesn't happen fast. App UI feels/appears frozen. I've never seen the spinner on 3.9 from what I can tell. Would be good to get someone to reproduce this, because I...

@wetneb isn't this a "good first issue" now for just about anyone with some light JS skills to change the code as suggested above?

I just wanted to point out this little fact that - for the variable, we have our docs stating otherwise, with the non-plural form `columnName` and not plural `columnNames` ,...

@wetneb I am OK for dynamic changes based on the checkboxes per cluster value and like that idea. What was your worry here about dynamic updates on each cluster as...