de-hardcode "/yancy/api", make configurable

lib/Mojolicious/Plugin/Yancy.pm

@@ -386,6 +386,7 @@ sub register {
     my ( $self, $app, $config ) = @_;
     my $yancy_path = $config->{yancy_path} // '/yancy';
     my $route = $config->{route} // $app->routes->any( $yancy_path );
+    my $api_path = $config->{api_path} // '/api';
     $route->to( return_to => $config->{return_to} // '/' );
     $config->{api_controller} //= 'Yancy::API';
 

lib/Yancy/Help/Config.pod

@@ -435,6 +435,11 @@ To customize the URL under which the Yancy editor is found. If not given,
 defaults to C</yancy>. Note, the various assets will still live on the
 web app under C</yancy>.
 
+=head2 C<api_path>
+
+To customize the URL under which the Yancy API is found. This will always
+be under the C<yancy_path> route. If not given, defaults to C</api>.
+
 =head1 SEE ALSO
 
 L<Yancy>, L<Mojolicious::Plugin::Yancy>

t/api.t

@@ -147,6 +147,25 @@ subtest 'different Yancy URL' => \&test_api,
     } ),
     '/yancy2/api';
 
+( $backend_url, $backend, %items ) = init_backend( $collections, %data );
+subtest 'different API URL' => \&test_api,
+    Test::Mojo->new( 'Yancy', {
+        backend => $backend_url,
+        collections => $collections,
+        api_path => '/api2',
+    } ),
+    '/yancy/api2';
+
+( $backend_url, $backend, %items ) = init_backend( $collections, %data );
+subtest 'different API and Yancy URLs' => \&test_api,
+    Test::Mojo->new( 'Yancy', {
+        backend => $backend_url,
+        collections => $collections,
+        yancy_path => '/yancy2',
+        api_path => '/api2',
+    } ),
+    '/yancy2/api2';
+
 subtest 'schema completely from database' => sub {
     my $t = Test::Mojo->new( Yancy => {
         read_schema => 1,