v0.1.0

This release had a major redesign to use modules for all the processing, as well as some other ui improvements.

The output from v0.1.0 is only slightly better than the original output, in that I fixed a few bugs I found along the way, e.g. in json request bodies. But more importantly the redesign will allow for adding modules to handle the various types of requests and data variations.

The types of modules that can be added are:

• processors - for processing various types of request data
• parsers - for extracting from various types of response data
• decoders - for decoding values extracted by processors and parsers
• encoders - for encoding values for parsers

Some examples of how this might work

• html form data processor extracts form data as key value pairs
• one of the form values was url encoded, so it's decoded by a decoder to plain text
• this plain text value is encoded by the various supported encoders
• the value was then found as a html encoded string in a previous response by a parser

Hopefully this design should handle the most complex of business workflows even when dealing with workflows that transverse applications that both use custom encodings.

I don't expect to need big changes to the core file now, mostly future releases should be about adding and updating modules 🤞

I've left this release marked as pre-release, it's quite likely there are bugs caused by moving code out to the modules and the various changes from this restructure.

• If your har file errors and fails to produce a .robot file, please if possible attach the har file to an issue so it can be fixed.
• If you har file produces a .robot file, but doesn't create a parameter for something it should have, if possible attach the har file to an issue so we can attempt to add a module for that type of value.