Skip Menu |

This queue is for tickets about the App-hr CPAN distribution.

Report information
The Basics
Id: 105641
Status: resolved
Priority: 0/
Queue: App-hr

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.11
Fixed in: (no value)



Subject: --json and --format=json?
Currently these options don't make hr generating json: $ /opt/perl-5.22.0/bin/hr --json | json_pp malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "====================...") at /usr/bin/json_pp line 44 And actually I can't think of a valid use case for such an option, so it's probably better to simplify the command and remove these options.
On 2015-07-03 01:45:52, SREZIC wrote: Show quoted text
> Currently these options don't make hr generating json: > > $ /opt/perl-5.22.0/bin/hr --json | json_pp > malformed JSON string, neither array, object, number, string or atom, > at character offset 0 (before "====================...") at > /usr/bin/json_pp line 44 > > And actually I can't think of a valid use case for such an option, so > it's probably better to simplify the command and remove these options.
... and --naked-res/--no-naked-res could also be removed.
Subject: Re: [rt.cpan.org #105641] --json and --format=json?
Date: Mon, 6 Jul 2015 15:10:36 +0700
To: bug-App-hr [...] rt.cpan.org
From: Perl Ancar <perlancar [...] gmail.com>
You're right. Removed in 0.12. Thanks! On Fri, Jul 3, 2015 at 12:47 PM, Slaven_Rezic via RT <bug-App-hr@rt.cpan.org Show quoted text
> wrote:
Show quoted text
> Queue: App-hr > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=105641 > > > On 2015-07-03 01:45:52, SREZIC wrote:
> > Currently these options don't make hr generating json: > > > > $ /opt/perl-5.22.0/bin/hr --json | json_pp > > malformed JSON string, neither array, object, number, string or atom, > > at character offset 0 (before "====================...") at > > /usr/bin/json_pp line 44 > > > > And actually I can't think of a valid use case for such an option, so > > it's probably better to simplify the command and remove these options.
> > ... and --naked-res/--no-naked-res could also be removed. >