I've been using Sourcery to generate documentation automatically for GitHub wiki (i.e. generate markdown files based on types & annotations), as it's pretty user friendly on there (as in "easy to read") and also very easy to do in templates thanks to Sourcery's capability to generate files on the fly.
However, using annotations is not very "coder-friendly" though, as it gets hard to maintain be
When developing templates sometimes you make an implementation mistake in a filter could be a simple cannot call method of undefined, however when that happens we receive no information about where in the filter the error occurred. It sometimes takes a lot of time to figure out where the error is really located, and sometimes the only approach is step by step console log and
fun url title ->
{ url = url
title = title }
|> fun f -> withFields (f)
|> fun codec ->
let decode = fst codec
let encode = snd codec
jfieldOpt ("url") (fun x -> x.url) (decode, encode)
|> fun codec ->
let decode = fst codec
let encode = snd codec
🧩 A library that generates kotlin code for Retrofit 2 based on a Swagger endpoint. Includes an Annotation Processor to configure and generate the code on build time.
I've been using Sourcery to generate documentation automatically for GitHub wiki (i.e. generate markdown files based on types & annotations), as it's pretty user friendly on there (as in "easy to read") and also very easy to do in templates thanks to Sourcery's capability to generate files on the fly.
However, using annotations is not very "coder-friendly" though, as it gets hard to maintain be