| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-05-03 | v1.4.0v1.4.0 | -1/+1 | ||
| 2023-05-03 | formatting fail | -2/+2 | ||
| 2023-05-03 | readme: big update that I'm too lazy to summarize | -61/+84 | ||
| 2023-05-03 | misc formatting changes | -5/+5 | ||
| 2023-04-16 | smtp: add smtp module and docs | -0/+222 | ||
| TODO: README and other meta-info, this isn't just http anymore | ||||
| 2023-04-16 | meta: fix compiles? | -3/+4 | ||
| 2023-04-16 | meta: test for ability to build statically | -5/+16 | ||
| 2023-04-16 | meta: use non-static config for now | -10/+19 | ||
| opens the way for static flags once I can test those | ||||
| 2023-04-16 | meta: improve build system | -5/+31 | ||
| use pkg-config! the main concern at this point is whether or not adding a "--static" is safe. if you don't add "--static", there's no guarantee of static linking. however, if you do add "--static" but not all of the libraries in question are available in static form, it will fail to build. the likely correct way to approach this is to use an env var. furthermore, I'm not entirely sure as to how/whether the link flags get passed on to upstream packages. | ||||
| 2023-04-10 | meta: prepare 1.3.0v1.3.0 | -1/+1 | ||
| new features, yay | ||||
| 2023-04-10 | janet: improve query handling, add part-appending | -6/+80 | ||
| also tests | ||||
| 2023-04-07 | meta: prepare for 1.2.0 releasev1.2.0 | -2/+2 | ||
| 2023-04-05 | meta: add basic slurp example to module docs | -0/+3 | ||
| 2023-04-05 | meta: improve doc formatting | -2/+2 | ||
| 2023-04-05 | meta: add tests for slurp and spit | -0/+22 | ||
| 2023-04-05 | update slurp/spit, stabilize, document | -9/+59 | ||
| after a short testing period, this'll be released | ||||
| 2023-04-05 | janet: spit: use body-plain | -1/+1 | ||
| to override content-type, simply change the content-type yourself it's meant to be an "easy to use" API, so defaults etc | ||||
| 2023-04-05 | janet: improve slurp/spit semantics | -13/+25 | ||
| 2023-04-05 | janet: add convenience functions slurp and spit | -0/+13 | ||
| these are currently to be considered unstable, fully undocumented. to be stabilized in an official release later, assuming they don't need any changes | ||||
| 2023-04-03 | meta: release 1.1.3v1.1.3 | -1/+1 | ||
| 2023-04-03 | native: fix non-zeroed initialization | -0/+11 | ||
| When we initialize an slist but it's meant to be empty, it might not be zero-allocated and thus recognize it's null. Therefore, explicitly zero-initialize jurl_cleanup->slist. | ||||
| 2023-04-03 | test: test json api | -0/+14 | ||
| 2023-04-03 | native: make strings more permissive | -6/+15 | ||
| * adds a getcbytes that accepts any JanetBytes * use it across the board, except where we can inform curl of the length | ||||
| 2023-04-02 | meta: update to 1.1.2v1.1.2 | -1/+1 | ||
| 2023-04-02 | native: fix gc allocation error in jurl :dup | -1/+1 | ||
| 2023-04-02 | meta: add more gitignores | -0/+2 | ||
| 2023-03-31 | meta: update readme for 1.1.1 releasev1.1.1 | -1/+1 | ||
| TODO: maybe set up a CHANGELOG? shotlog is nice and all but you know | ||||
| 2023-03-31 | meta: update README re: inclusion in jpm | -1/+5 | ||
| 2023-03-29 | tests: add test for oauth | -0/+14 | ||
| 2023-03-29 | janet: fix oauth | -1/+1 | ||
| 2023-03-28 | meta: add information about curl versioning | -0/+4 | ||
| 2023-03-28 | native: fix compat with curl as old as 7.81.0 | -0/+8 | ||
| 2023-03-28 | meta: change recommended tag to 1.1.0v1.1.0 | -1/+1 | ||
| 2023-03-28 | meta: add TECH.md | -0/+95 | ||
| 2023-03-28 | meta: all the tests | -1/+235 | ||
| ok not all the tests just testing the high level api the other top level things would be: 02-request and 01-native probably to be done native mostly useful for regression testing and seeing what went wrong where for example, if the high level api is what broke, and not request or if it was the native stuff that broke, and not anything else etc | ||||
| 2023-03-28 | meta: depend on spork | -1/+2 | ||
| 2023-03-28 | janet: add body-type and co, fix PUTs and bodies | -11/+36 | ||
| writing tests reveals issues, as per usual also rejoice, you have json I gave up and am depdending on spork/json now | ||||
| 2023-03-28 | meta: readme indentationv1.0.0 | -6/+6 | ||
| I really should fix my markdown handling it should know to use janet formatting inside ```janet | ||||
| 2023-03-28 | meta: update readme to current state of the project | -23/+71 | ||
| 2023-03-28 | janet: finish module docs | -6/+38 | ||
| 2023-03-28 | janet: add documentation to pipeline api | -6/+60 | ||
| 2023-03-28 | janet: improve defapi to do smarter merging | -22/+23 | ||
| this means I can simplify all the defapi calls | ||||
| 2023-03-28 | janet: move handle into request as client | -2/+4 | ||
| 2023-03-27 | janet: initial fancy api preview | -0/+59 | ||
| 2023-03-27 | janet: fix mime-related bug | -13/+19 | ||
| tl;dr mimepost is at odds with post so if we mimepost, do not change method this means you cannot mimepost with a put but that's probably fine | ||||
| 2023-03-27 | janet: format using %V | -4/+4 | ||
| 2023-03-27 | janet: pass in cookies | -2/+4 | ||
| 2023-03-27 | native: correct classification mistake | -2/+2 | ||
| cookiejar etc just take a filename | ||||
| 2023-03-26 | meta: readme s/\t/ /g | -5/+5 | ||
| 2023-03-26 | meta: add installation cmd | -0/+2 | ||
