Warning on unique object type fields

[sleepinggenius2]

Plugin Version

0.3.1

NetBox Version

4.4.1

Python Version

3.12

Steps to Reproduce

1. Create a custom object type
   • Internal name = "test"
   • URL path/slug = "test"
2. Add Field
   • Name = "device"
   • Type = Object
   • Must be unique = True
   • Related object type = DCIM > Device
3. Start the NetBox service using manage.py runserver

Expected Behavior

Service should start up cleanly with no errors or warnings.

Observed Behavior

The following appears on the console at startup:

Watching for file changes with StatReloader
Performing system checks...

System check identified some issues:

WARNINGS:
netbox_custom_objects.Table1Model.device: (fields.W342) Setting unique=True on a ForeignKey has the same effect as using a OneToOneField.
	HINT: ForeignKey(unique=True) is usually better served by a OneToOneField.
netbox_custom_objects.Table1Model.device: (fields.W342) Setting unique=True on a ForeignKey has the same effect as using a OneToOneField.
	HINT: ForeignKey(unique=True) is usually better served by a OneToOneField.

[mrmrcoleman]

Tested at:

NetBox: 4.4.1 (NetBox Docker)
Custom Objects: commit e93de4b8771d7499b37a73ac0da7bd453dc73896 (HEAD -> main, origin/main, origin/HEAD)

---

After following the steps above I did:

docker compose down
docker compose up -d

Reproduced:

netbox-worker-1  | System check identified some issues:
netbox-worker-1  | 
netbox-worker-1  | WARNINGS:
netbox-worker-1  | netbox_custom_objects.Table1Model.device: (fields.W342) Setting unique=True on a ForeignKey has the same effect as using a OneToOneField.
netbox-worker-1  |      HINT: ForeignKey(unique=True) is usually better served by a OneToOneField.
netbox-worker-1  | netbox_custom_objects.Table1Model.device: (fields.W342) Setting unique=True on a ForeignKey has the same effect as using a OneToOneField.
netbox-worker-1  |      HINT: ForeignKey(unique=True) is usually better served by a OneToOneField.