Daniel Gruno

the token fetched from the preferences URI must currently be handed in the Kibble-Token header of the request, such as in this python example: ~~~python issues = requests.post('https://demo.kibble.apache.org/api/issue/issues', headers =...

I'll also add that the token should be easily visible to the user, which means working on the user interface some more..

Known issue, happens because you don't have a cookie set before your browser visits the login API URL. There are basically two ways we can address this: 1. fix the...

I'm doing the same for another project I work on. 7+ generally works as kibble installations are most often standalone and thus not tied to an old legacy database or...

Good idea - what about maybe an icon to the right of them for opening in a new tab? Some people might prefer the URL stays as a textNode, to...

Can you redo the kibble.v1.js with the added changes to master, please? That way we can merge the changes.

Would it be better if, instead of having a queryMethod attribute, this was changed to be a PATCH request? that way, a PUT would create a new org, and a...

I suspect the JS is forcing integer values. I'll look into that. Perhaps we need to add an extra argument to the JSON output to specify that this is a...

oh, I see the issue. You have to specify in python (2.7 at least) that you want a floating point result, or it will turn it into an integer. Something...

This looks like pretty standard behavior from Elastic, breaking backwards compatibility. The quickest solution would be to use ElasticSearch 7.x instead (or at least the 7.x python client module).