LocalKey not working with a HAS_ONE relationship

[MrAtiebatie]

I had the following database scheme:

users

• id
• name
• language_id

languages

• id
• name

Now I have tried to make the relationship between language_id and languages.id:

But after an hour debugging I found out that he didn't used the localKey but just the primary key of the table, in the case of the user table it's 'id'. So I took a look in the source of Ardent and saw that the localKey parameter isn't sent to Model@hasOne while it is an (optional) parameter of the hasOne method of Laravel. Is this a bug? Because when I changed rule 316&317 in Ardent.php it worked:

Thanks in advance

[VesninAndrey]

Also came across this feature. Please add the "localKey" for relations HAS_ONE, HAS_MANY and BELONGS_TO.

For those looking for a quick solution - make like issue author:

(start at line 313 in Ardent.php)
case self::HAS_ONE:
case self::HAS_MANY:
case self::BELONGS_TO:
$verifyArgs(['foreignKey', 'localKey']);
return $this->$relationType($relation[1], $relation['foreignKey'], $relation['localKey']);

[misilot]

What would need to be done to get this included in a release?

[gg4you]

Has this been included in a release?

[igorsantos07]

this might be something that was added later and not looked into at the time of development.

Just wondering: is your field was language_id why is the local key only language? haha