Pedantic change of 'hash-ref' to 'hash reference'
Packy Anderson
7 years ago
80 | 80 | } |
81 | 81 | |
82 | 82 | $rest_client_config = {} unless defined $rest_client_config; |
83 | croak __PACKAGE__ . "::new: REST_CLIENT_CONFIG argument must be a hash-ref.\n" | |
83 | croak __PACKAGE__ . "::new: REST_CLIENT_CONFIG argument must be a hash reference.\n" | |
84 | 84 | unless |
85 | 85 | defined $rest_client_config |
86 | 86 | && ref $rest_client_config |
255 | 255 | $path = $self->{path} . $path unless $path =~ m:^/rest/:; |
256 | 256 | |
257 | 257 | if (defined $query) { |
258 | croak $self->_error("The QUERY argument must be a hash-ref.") | |
258 | croak $self->_error("The QUERY argument must be a hash reference.") | |
259 | 259 | unless ref $query && ref $query eq 'HASH'; |
260 | 260 | return $path . '?'. join('&', map {$_ . '=' . uri_escape($query->{$_})} keys %$query); |
261 | 261 | } else { |
595 | 595 | =item * VALUE |
596 | 596 | |
597 | 597 | This is the "entity" being PUT or POSTed. It can be any value, but |
598 | usually is a hash-ref. The value is encoded as a | |
598 | usually is a hash reference. The value is encoded as a | |
599 | 599 | L<JSON|http://www.json.org/> string using the C<JSON::encode> method |
600 | 600 | and sent with a Content-Type of C<application/json>. |
601 | 601 | |
622 | 622 | |
623 | 623 | The majority of the API's resources return JSON values. Those are |
624 | 624 | decoded using the C<decode> method of a C<JSON> object. Most of the |
625 | endpoints return hashes, which are returned as a Perl hash-ref. | |
625 | endpoints return hashes, which are returned as a Perl hash reference. | |
626 | 626 | |
627 | 627 | =item * text/plain |
628 | 628 | |
668 | 668 | |
669 | 669 | =head2 B<set_search_iterator> PARAMS |
670 | 670 | |
671 | Sets up an iterator for the search specified by the hash-ref PARAMS. It must | |
672 | be called before calls to B<next_issue>. | |
671 | Sets up an iterator for the search specified by the hash reference PARAMS. | |
672 | It must be called before calls to B<next_issue>. | |
673 | 673 | |
674 | 674 | PARAMS must conform with the query parameters allowed for the |
675 | 675 | C</rest/api/2/search> JIRA REST endpoint. |