libdnf's GObjects have many setters and getters but no properties about libdnf HOT 3 CLOSED

@Bob131 This is absolutely the right time to mention this! libdnf does not yet have a fixed API, and that will only occur once its first release is made.

from libdnf.

Please if the issue is still valid, please could you open the new bugzilla with updated information like what kind of informition you are interest for which purpose?

from libdnf.

• DnfRepo is declared as a derivable type, but to get a functioning instance dnf_repo_new must be called since it sets a private field. Either DnfRepo needs to be a final type or context made a construct property.
• DnfRepo has (at least) 11 getter/setter pairs that ought to be properties:
  • dnf_repo_{get,set}_id
  • dnf_repo_{get,set}_location
  • dnf_repo_{get,set}_filename
  • dnf_repo_{get,set}_packages
  • dnf_repo_{get,set}_enabled
  • dnf_repo_{get,set}_required
  • dnf_repo_{get,set}_cost
  • dnf_repo_{get,set}_module_hotfixes
  • dnf_repo_{get,set}_kind
  • dnf_repo_{get,set}_gpgcheck
  • dnf_repo_{get,set}_gpgcheck_md

As mentioned above, properties bring many benefits: notify signals, GBindings, property overrides, better GI bindings, convenience functions like g_object_set, etc. For instance, I have a use case for which it would be convenient to be able to bind the enabled property of several repo objects together.

• DnfPackage is declared as a derivable type, but to get a functioning instance dnf_package_new must be called since it sets private fields. Either DnfPackage needs to be a final type or sack and id made construct properties.

• DnfContext also has a large number of get/set functions. Being able to set/get more than one property at a time with g_object_{set,get} would be espeically handy for an object like DnfContext, but the other above-mentioned benefits also apply here.

from libdnf.