Another heavy refactor of the rel resolver prototype (sequel to 03f6d1f7)

[dbsrgits/DBIx-Class.git] / t / relationship / custom.t

diff --git a/t/relationship/custom.t b/t/relationship/custom.t
index 0cf32b5..10ab27c 100644 (file)
--- a/t/relationship/custom.t
+++ b/t/relationship/custom.t
@@ -151,15 +151,20 @@ is_deeply(
 
 } 'prefetchy-fetchy-fetch';
 
+# create_related a plain cd via the equoivalent coderef cond, with no extra conditions
+lives_ok {
+  $artist->create_related('cds_cref_cond', { title => 'related creation via coderef cond', year => '2010' } );
+} 'created_related with simple condition works';
 
 # try to create_related a 80s cd
 throws_ok {
   $artist->create_related('cds_80s', { title => 'related creation 1' });
-} qr/\QCustom relationship 'cds_80s' not definitive - returns conditions instead of values for column(s): 'year'/,
+} qr/\QUnable to complete value inferrence - custom relationship 'cds_80s' returns conditions instead of values for column(s): 'year'/,
 'Create failed - complex cond';
 
 # now supply an explicit arg overwriting the ambiguous cond
-my $id_2020 = $artist->create_related('cds_80s', { title => 'related creation 2', year => '2020' })->id;
+my $cd_2020 = $artist->create_related('cds_80s', { title => 'related creation 2', year => '2020' });
+my $id_2020 = $cd_2020->id;
 is(
   $schema->resultset('CD')->find($id_2020)->title,
   'related creation 2',
@@ -268,4 +273,21 @@ is_deeply (
   'Prefetched singles in proper order'
 );
 
+# test set_from_related with a belongs_to custom condition
+my $cd = $schema->resultset("CD")->find(4);
+$artist = $cd->search_related('artist');
+my $track = $schema->resultset("Track")->create( {
+  trackid => 1,
+  cd => 3,
+  position => 99,
+  title => 'Some Track'
+} );
+$track->set_from_related( cd_cref_cond => $cd );
+is ($track->get_column('cd'), 4, 'set from related via coderef cond');
+is_deeply (
+  { $track->cd->get_columns },
+  { $cd->get_columns },
+  'set from related via coderef cond inflates properly',
+);
+
 done_testing;