view release on metacpan or search on metacpan
lib/CatalystX/Action/ExtJS/REST.pm view on Meta::CPAN
#
# The (three-clause) BSD License
#
package CatalystX::Action::ExtJS::REST;
$CatalystX::Action::ExtJS::REST::VERSION = '2.1.3';
# ABSTRACT: Mark an action as REST endpoint
use Moose;
extends 'Catalyst::Action';
1;
view release on metacpan or search on metacpan
lib/Catalyst/ActionRole/OAuth2/AuthToken/ViaAuthGrant.pm view on Meta::CPAN
package Catalyst::ActionRole::OAuth2::AuthToken::ViaAuthGrant;
use Moose::Role;
use Try::Tiny;
use CatalystX::OAuth2::Request::AuthToken;
# ABSTRACT: Authorization token provider endpoint for OAuth2 authentication flows
with 'CatalystX::OAuth2::ActionRole::Token';
sub build_oauth2_request {
view release on metacpan or search on metacpan
lib/Catalyst/ActionRole/RequestModel.pm view on Meta::CPAN
}
The main reason for moving this into the action attributes line is the thought that it allows us
to declare the request model as meta data on the action and in the future we will be able to
introspect that meta data at application setup time to do things like generate an Open API specification.
Also, if you have several request models for the endpoint you can declare all of them on the
attributes line and we will match the incoming request to the best request model, or throw an exception
if none match. So if you have more than one this saves you writing that boilerplate code to chose and
to handled the no match conditions.
You might also just find the code neater and more clean reading. Downside is for people unfamiliar with
view release on metacpan or search on metacpan
lib/Catmandu/AAT.pm view on Meta::CPAN
Catmandu::AAT - Retrieve items from the AAT
=head1 SYNOPSIS
This module contains a L<store|Catmandu::Store::AAT> to lookup a I<Subject> in the L<AAT|https://www.getty.edu/research/tools/vocabularies/aat/>
using its L<SPARQL endpoint|http://vocab.getty.edu/sparql>.
Also included is a L<fix|Catmandu::Fix::aat_match> to match a term to a I<Subject> and a
L<fix|Catmandu::Fix::aat_search> to search for a term in the AAT.
lookup_in_store(objectName, AAT, lang:nl)
view release on metacpan or search on metacpan
lib/Catmandu/Adlib.pm view on Meta::CPAN
Catmandu::Adlib - Catmandu interface to L<Adlib|http://www.adlibsoft.nl/>
=head1 SYNOPSIS
# From the command line
catmandu export Adlib to YAML --id 1234 --endpoint http://test2.adlibsoft.com --username foo --password bar --database collect.inf
# From a Catmandu Fix
lookup_in_store(
object_priref,
Adlib,
endpoint: http://test2.adlibsoft.com,
username: foo,
password: bar,
database: collect.inf
)
view release on metacpan or search on metacpan
lib/Catmandu/Importer/ArXiv.pm view on Meta::CPAN
=over
=item base_api
The API endpoint. Default is https://export.arxiv.org/api/query
=item base_frontend
The arXiv base url. Default is https://arxiv.org
view release on metacpan or search on metacpan
requires 'REST::Client', '0';
requires 'Moo', '0';
requires 'URI::Escape', '0';
requires 'JSON::MaybeXS', '>=1.003005';
# Need recent SSL to talk to https endpoint correctly
requires 'IO::Socket::SSL', '>=1.993';
view release on metacpan or search on metacpan
requires 'HTTP::Request::Common', '6.04';
requires 'RDF::Trine', '1.014';
requires 'Test::JSON', '0.11';
requires 'XML::LibXML', '2.0121';
# Need recent SSL to talk to https endpoint correctly
requires 'IO::Socket::SSL', '2.015';
view release on metacpan or search on metacpan
lib/Catmandu/Importer/OpenAIRE.pm view on Meta::CPAN
# From the command line
# Harvest some data
catmandu convert OpenAIRE to YAML
# Harvest some data from a different endpoint
catmandu convert OpenAIRE --url http://api.openaire.eu/search/datasets to YAML
=head1 DESCRIPTION
See L<https://graph.openaire.eu/develop/api.html> for the OpenAIRE query parameters
view release on metacpan or search on metacpan
lib/Catmandu/Exporter/MediaHaven.pm view on Meta::CPAN
=over
=item url
Required. The URL to the MediaHaven REST endpoint.
=item username
Required. Username used to connect to MediaHaven.
view release on metacpan or search on metacpan
lib/Catmandu/Importer/OAI.pm view on Meta::CPAN
$ catmandu convert OAI --url http://myrepo.org/oai --getRecord 1 --identifier oai:myrepo:1234
=head1 DESCRIPTION
L<Catmandu::Importer::OAI> is an L<Catmandu> importer to harvest metadata records
from an OAI-PMH endpoint.
=head1 CONFIGURATION
=over
view release on metacpan or search on metacpan
lib/Catmandu/Importer/Pure.pm view on Meta::CPAN
our $VERSION = '0.05';
with 'Catmandu::Importer';
has base => ( is => 'ro' );
has endpoint => ( is => 'ro' );
has path => ( is => 'ro' );
has apiKey => ( is => 'ro' );
has user => ( is => 'ro' );
has password => ( is => 'ro' );
has post_xml => ( is => 'ro' );
view release on metacpan or search on metacpan
lib/Catmandu/Importer/Solr.pm view on Meta::CPAN
)->total();
}
=head1 NAME
Catmandu::Importer::Solr - Catmandu module to import data from a Solr endpoint
=head1 SYNOPSIS
# From the command line
$ catmandu convert Solr --url "http://localhost:8983/solr" --query "type:book"
view release on metacpan or search on metacpan
lib/Catmandu/Fix/aat_match.pm view on Meta::CPAN
-lang: nl
)
=head1 DESCRIPTION
Perform a direct match between a term and the L<SPARQL endpoint|http://vocab.getty.edu/sparql> of the AAT.
This fix will attempt to find a I<Subject> for which the I<prefLabel> in I<lang> (optional, default C<nl>)
equals the term. Will return a single item if one is found, or an empty hash if none was found.
Returns the following data:
view release on metacpan or search on metacpan
lib/Catmandu/Store/REST.pm view on Meta::CPAN
=encoding utf-8
=head1 NAME
Catmandu::Store::REST - Store/retrieve items from a JSON REST-API endpoint
=head1 SYNOPSIS
# From the command line
$ catmandu export REST --id 1234 --base_url https://www.example.org/api/v1/books --query_string /page/1 to YAML
view release on metacpan or search on metacpan
t/001_parse/ec2_volume.res
t/001_parse/ec2_volume2.res
t/001_parse/ec2_volumeattachment.res
t/001_parse/ec2_vpc.res
t/001_parse/ec2_vpc_dhcp_options.res
t/001_parse/ec2_vpc_endpoint.res
t/001_parse/ec2_vpc_gw_attach.res
t/001_parse/ec2_vpc_gw_vpn.res
t/001_parse/ec2_vpccidrblock.res
t/001_parse/ec2_vpn_conn.res
t/001_parse/ec2_vpn_gw.res
view release on metacpan or search on metacpan
lib/Chart/Plotly/Trace/Scatter.pm view on Meta::CPAN
has fill => (
is => "rw",
isa => enum( [ "none", "tozeroy", "tozerox", "tonexty", "tonextx", "toself", "tonext" ] ),
documentation =>
"Sets the area to fill with a solid color. Defaults to *none* unless this trace is stacked, then it gets *tonexty* (*tonextx*) if `orientation` is *v* (*h*) Use with `fillcolor` if not *none*. *tozerox* and *tozeroy* fill to x=0 and y=0 respect...
);
has fillcolor => (
is => "rw",
isa => "Str",
view release on metacpan or search on metacpan
lib/Chess/Board.pm view on Meta::CPAN
Takes a single scalar parameter containing the square to calculate distance
from. Returns the vertical distance in squares between the two points.
=item squares_in_line()
Takes two scalar parameters containing two distinct endpoints in a line.
Returns a list of scalars in lower-case with an entry for each square in that
line, or C<undef> if the two endpoints do not define a line. In the case where
both squares are the same, will return a list containing that square.
=back
=head2 Object methods
view release on metacpan or search on metacpan
t/autodb.020.graph/graph.010.01.thaw_nodes.t view on Meta::CPAN
$ok&&=_cmp_thawed(\@all_actual_objects,\@correct_thawed,
"$label thawed edges",__FILE__,__LINE__);
}
report_pass($ok,"$label thawed edges");
# check edges' nodes (aka endpoints) - nodes should all be thawed already
my @actual_ends=map {@{$_->nodes}} @actual_edges;
cmp_thawed(\@actual_ends,\@actual_nodes,"$label thawed edge endpoints");
local $SIG{__WARN__}=sub {warn @_ unless $_[0]=~/^Deep recursion/;};
local $DB::deep=0;
# test contents the usual way.
view release on metacpan or search on metacpan
azure-pipelines.yml view on Meta::CPAN
resources:
repositories:
- repository: ci-perl-helpers
type: github
name: houseabsolute/ci-perl-helpers
endpoint: houseabsolute
stages:
- template: templates/helpers/build.yml@ci-perl-helpers
parameters:
debug: true
view release on metacpan or search on metacpan
lib/Color/Spectrum/Multi.pm view on Meta::CPAN
# take the first colour waypoint off:
my $startpoint = shift @points;
# How many steps do we get between each waypoint?
my $substeps = int($steps / scalar @points);
while(my $endpoint = shift @points) {
if (@points == 0) {
# there's no more points left... make sure we don't fall short
# on the number of steps:
if (($steps_used + $substeps) != $steps) {
$substeps = $steps - $steps_used;
view release on metacpan or search on metacpan
lib/Config/Model/models/Systemd/Section/Socket.pl view on Meta::CPAN
'cargo' => {
'type' => 'leaf',
'value_type' => 'uniline'
},
'description' => 'Specifies a L<USB
FunctionFS|https://docs.kernel.org/usb/functionfs.html> endpoints location to listen on, for
implementation of USB gadget functions. This expects an
absolute file system path of a FunctionFS mount point as the argument.
Behavior otherwise is very similar to the C<ListenFIFO>
directive above. Use this to open the FunctionFS endpoint
C<ep0>. When using this option, the
activated service has to have the
C<USBFunctionDescriptors> and
C<USBFunctionStrings> options set.
',
view release on metacpan or search on metacpan
lib/Confluence/Client/XMLRPC.pm view on Meta::CPAN
The package uses the L<RPC::XML> module to do the heavy lifting. Read the
perldoc for this package to learn more.
L<RPC::XML> uses LWP for handling C<http>/C<https> messaging. If you are
experiencing problems when connecting to a C<https> based API endpoint,
please make sure that the necessary modules - like, e.g.
L<LWP::Protocol::https> - are installed.
For further information on the Confluence API itself please refer to the
L<official documentation|https://developer.atlassian.com/display/CONFDEV/Confluence+XML-RPC+and+SOAP+APIs>