Add dbus.ParseProperties and dbus.ParseOptions
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.7k
- Forks
- 338
- PR merge metrics
- No merged PRs in 30d
Description
ParseProperties(props []Property, unitType string) ([]_unit.UnitOption, error)
ParseOptions(opts []_unit.UnitOption) ([]Property, string, error)
From what I can tell, all the unit options [1] map into dbus properties [2](though the reverse is not true, of course). I've done something like this for a limited sub-set, but it would be helpful for a number of reasons if this functionality existed upstream (here).
[1] http://www.freedesktop.org/software/systemd/man/systemd.directives.html
[2] http://www.freedesktop.org/wiki/Software/systemd/dbus/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the systemd directives and D-Bus references linked in the issue, then inspect the repository's existing unit-option and D-Bus property types. Define the mappings required by ParseProperties and ParseOptions, including how unsupported or invalid values are reported. Done means both functions provide the requested conversions and the relevant Go tests cover them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100