Discussion: Relationships support about fireorm HOT 3 OPEN

Yeah I thought something similar, but the problem is that the relation field will be initialize as a function, but then it'll be updated with the actual data, and I don't want that.

Given this entity:

export class Band {
  id: string;
  name: string;
  formationYear: number;
  genres: Array<string>;

  @OneToMany(Album, (album, band) => a.bandId === band.id, {lazy: true})
  albums: ISubCollection<Album>;
}

const band = await bandRepository.findById('three-days-grace');
// Calling band.albums to retrieve the albums
await band.albums();

// Now albums is not a function anymore
console.log(band.albums)

Note: that syntaxis is not final, haven't had time to actually design how it would work

from fireorm.

I'll start thinking about this as well. My initial thoughts are regarding this question:

Promises are eagerly evaluated, how the Lazy Promise implementation would look like.

A possible solution to this would be to create a function that returns the "Lazy Promise". This will ensure that the "Lazy Promise" will only begin executing when we call the function that returns the "Lazy Promise".

Something like:

function createLazyPromise() {
    const lazyPromise = new Promise((resolve, reject) => {
        // execute query
    });
    return lazyPromise;
}
// lazyPromise has not begun "executing" here, since the `createLazyPromise` function hasn't been called yet.

from fireorm.

Started with the actual implementation, a lot of things are missing.

from fireorm.