-
Notifications
You must be signed in to change notification settings - Fork 35
The server.go example is not properly introspectable #27
Comments
The example is supposed to be just this - a simple, minimalist example. You're right, though, in that there should be something to make this easier for real cases. I'll leave this open as a reminder. |
could someone describe what the correct solution is? is it to create the whole path as Nodes under a root Node? |
I did this: Now dbus introspect tools don't throw errors about non-existent objects. |
you can check this pull request #34 this commit will handle this problem snyh@a1afa96 |
Hello, based on @snyh's work, I created a pull request that addresses simply the introspection of "sub-paths" of exported objects. You can look it up here: #53, please let me know what you think. There are other interesting things in @snyh's pull request, such as helpers to automatically generate properties/signals introspection data, the same way the Methods helper does. I think these would be nice things to have, but this is another matter. |
Add ExportWithMap method.
The Introspect method is only implemented on the /com/github/guelfey/Demo path so
Returns the right xml while the following does not:
The right output would be this:
calling /com should return the github node and so on.
I think there is no tool in the introspect package to generate these.
The text was updated successfully, but these errors were encountered: