Closed dehnert closed 11 years ago
Coverage decreased (-1.46%) when pulling b941289645b506d07c3e61272c3e2c77d196d71d on dehnert:rtrc into 9a9fd7ac31ef7968d530dddcbe76fbf3a7a5f78c on z4r:master.
I like your idea, but I would prefer some kind of standard (json, yaml, ini). In addition we should add the same helper to the tracker.
Do you agree?
I like your idea, but I would prefer some kind of standard (json, yaml, ini).
The ~/.rtrc file is "standard" insofaras it's automatically used by the "rt" command line client distributed with RequestTracker. It seems a pity not to support the config file that upstream is using, regardless of whether we also support JSON/YAML/ini/???.
In addition we should add the same helper to the tracker.
Tracker
inherits from RTResource
, so Tracker.from_rtrc(auth)
will work as-is.
Ok, i've to stop to reply just awake :)
I didn't know about the rt
command.
During the day I'll merge and i'll add some test.
Thx
A common connection scheme is probably to read the server, username, and/or password out of the ~/.rtrc file. Facilitate this process so that API clients don't need to implement the file-reading themselves.