Idea: Generic Dict Data Mapper about jc

[kellyjonbrazil]

#4 (bytes) I can probably remove that code and use utils.convert_size_to_int() now.

#5 (remove quotes) can probably be added to utils as a function.

#6 (normalize keys) can probably be added to utils as a function.

The dict mapper idea is not a bad one, but probably not at the top of my priority list at the moment.

[muescha]

I have made some initial attempts as a personal exploration:

I currently have a draft version, but I am not entirely satisfied with it :(

You can find the code here:

• Implementation: dict_mapper.py
• Test cases: test_dict_mapper.py

The issue I am facing is that I initially examine item_mappings and then move on to key_mappings. However, the resulting changes are not as predictable for the end user.

I believe implementing changes in a pipeline would be more effective, allowing users to define the order themselves:

mapper_options = Pipeline([
	# find matches and add results to the dict
	UpdateMapper({'http-update': matcher}),

	KeyMapper({
		'version' : 'HTTP-Version',
		'status_code': 'Status-Code',
		'status_reason': 'Status-Reason'
    }),
	KeyMapper('replace_this_key', 'replaced_key'),
	KeyMapper({'.+_change$': lambda x: x.lower()}),

	ValueMapper({'*': lambda x: x.upper()})
])

• KeyMapper = update a key key = change(key)
• ValueMapper = update the value value = change(value)
• UpdateMapper = add key:values to the data dict = change(key, value)
• ItemMapper = change the value, the function signature is value = change(key,value)

[muescha]

... can probably be added to utils as a function.

yes the idea was to map helper functions (maybe all placed in utils.converter) to some dict values identified by keys.

The dict mapper idea is not a bad one, but probably not at the top of my priority list at the moment.

yes - you are right - the mapper would be out of scope of jc

While I think more about it: it is better to have it KISS than a bunch of additional code to just replace one-liners

I will close this issue, maybe reopen it when I have better and leaner implementation available