Update README

[fizruk]

README does not currently mention Form, LenientData or any of the useful helper functions.
Also it does not get typechecked. We should probably update README to give an up-to-date description of what this package provides.

[phadej]

markdown-unlit and doctest doesn't seem to play well together, do they?

One option is to make Web.FormUrlEncoded.Tutorial with most tutorial content from README. (unfortunately we don't have single main module in this package)

[fizruk]

@phadej do you think we should restructure modules?

Currently we have

Web
├── FormUrlEncoded
├── HttpApiData
└── Internal
    ├── FormUrlEncoded
    └── HttpApiData

And I would like to add some support for multipart/form-data soon.
It might be good to restructure modules in the same release we add that.

How about making Web.HttpApiData main module like this?

Web
└── HttpApiData
    ├── Internal
    │   ├── FormUrlEncoded
    │   ├── HttpApiData
    │   └── MultiPartFormData
    ├── FormUrlEncoded
    ├── HttpApiData
    ├── MultiPartFormData
    └── Tutorial

[phadej]

👍

…

Sent from my iPhone

On 21 Feb 2018, at 15.30, Nickolay Kudasov ***@***.***> wrote: @phadej do you think we should restructure modules? Currently we have Web ├── FormUrlEncoded ├── HttpApiData └── Internal ├── FormUrlEncoded └── HttpApiData And I would like to add some support for multipart/form-data soon. It might be good to restructure modules in the same release we add that. How about making Web.HttpApiData main module like this? Web └── HttpApiData ├── Internal │ ├── FormUrlEncoded │ ├── HttpApiData │ └── MultiPartFormData ├── FormUrlEncoded ├── HttpApiData ├── MultiPartFormData └── Tutorial — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.