1. The extra data is expected to be a json, so you can convert it to a sensible data structure, see get_build() and _fix_extra_field()
2. As the result of listTagged usually contains a number of items, and extra data are too big or not necessary to display, we could have an option to turn it on/off.

@julian8628 both fixed

and more here:
1. The rpm and archive entities both have an extra field too, so maybe we could bring the option to readTaggedRPMS and listTaggedArchives (readTaggedArchives) as well?
2. the docstrings could be updated to honor the new option

@julian8628 fixed and I fixed also issue #3283 in this PR.

for backward compatibility, the default extra of listTaggedArchives and listTaggedRPMS should be True

Otherwise, :thumbsup:

@julian8628 good catch, fixed.

:thumbsup:

:thumbsup:

Ouch, now've seen #3283 - we can't rename deliberately that option. Let's stay with 'type' for now. Maybe we could create separate PR with new alias option (while still having the old one) and deprecation warning but can't remove it directly.

You can call __builtins__.type(arch) instead to refer to overridden method. (or theoretically better import builtins; builtins.type(arch) - but we don't expect to run anything else than cPython.

@tkopecek ok, I'll do this change for type in the separate PR. This PR is related to extra option only.

Commit 87aa8eb1 fixes this pull-request