Skip Menu |
 

This queue is for tickets about the Catalyst-View-JSON CPAN distribution.

Report information
The Basics
Id: 53461
Status: rejected
Priority: 0/
Queue: Catalyst-View-JSON

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

Bug Information
Severity: Normal
Broken in: 0.26
Fixed in: (no value)



Subject: Documentation: clarify configured module name
The documentation for Catalyst::View::JSON states that the configuration values should be under the "View::JSON" key.  This could apply to one of two things in the document: the Catalyst::View::JSON module itself or the MyApp::View::JSON view that is created as an example.

I think it would be best to disambiguate this: either rename the example package to something that does not contain the View::JSON string (MyApp::View::API::JSON, maybe?) or explicitly state that the configuration key corresponds to the name of the Catalyst view.
Download (untitled) / with headers
text/plain 169b
I understand the possible confusion here but this would be better in the core catalyst docs since basically its the same problem for every view (or model or controller).


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.