4 commits

Author	SHA1	Message	Date
Thomas Haller	1dbbf6fb03	libnm: track invalid user data separately and reject during verify() ... nm_setting_user_set_data() rejects invalid keys and values, and can fail. This API is correct never to fail, like the get_data() only returns valid user-data. However, the g_object_set() API allows to set the hash directly but it cannot report errors for invalid values. This API is used to initialize the value from D-Bus or keyfile, hence it is wrong to emit g_critial() assertions for untrusted data. It would also be wrong to silently drop all invalid date, because then the user cannot get an error message to understand what happend. The correct but cumbersome solution is to remember the invalid values separately, so that verify() can report the setting as invalid.	2017-05-06 14:12:18 +02:00
Beniamino Galvani	a4cbfe6f0a	all: fix typo 'entires' -> 'entries'	2017-05-05 19:14:19 +02:00
Thomas Haller	23298bfc88	cli: move utils function from common.h to nm-meta-setting-desc.c ... These functions are only used by nm-meta-setting-desc.c. Make them internal. Unfortunately, they are part of "common.h" which cannot be used without the rest of nmcli. Still todo.	2017-03-30 13:09:58 +02:00
Thomas Haller	4ec7dd987e	libnm: add NMSettingUser ... This only adds new API for a NMSettingUser. The setting class is still entirely unused. The point is getting the new API into 1.8.0 release of libnm. It's easier to backport the use of the API to a stable branch then backporting public API. https://bugzilla.gnome.org/show_bug.cgi?id=776276 https://bugzilla.redhat.com/show_bug.cgi?id=1421429	2017-03-28 14:58:21 +02:00