Use of localized for relationships

[dapper orbit]

Hi.

I have a collection called Categories where I keep category entries for Posts. I have a question regarding handling of the Category field in the Posts collection using the relationship type. In the Category collection the title field has localized: true. Do I need to do the same and use localized: true for the category field in the Posts collection where I use the relationship type? I did that as below but it seems redundant as the db entries for all locale entries are the same with reference to the same object id from the Categories collection. Thanks.

// Posts.ts
...
    {
      name: 'category',
      label: 'Category',
      type: 'relationship',
      relationTo: 'categories',
      required: true,
      localized: true,
    },
...

[dusk crown]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Join Field - Using the Join field to have full control of your database schema - Specifying additional fields on relationships
• Versions
• Join Field
• Drafts - Draft API - Reading drafts vs. published documents
• Jobs

Community-Help:

• Bug?: Where Query on Relationships

[zinc drum]

I don't think so.
As far as I know localized: true, shows that it can be different content on other locales.
So if categories in post don't change on different locales - it's optional.

[dapper orbit]

It makes more sense that way but the documentation for the relationship field lists localized as a viable key as shown here:
https://payloadcms.com/docs/fields/relationship#config-options
So, I am still not sure.