[Brains as Chatflow]

[Chloeroumengas]

Why do we need this functionality?

X

What are we developing?

X

What are the validation criteria to validate this feature?

X

What's out of scope for this feature?

X

Should this feature be feature flagged?

• Feature Flagged

How are we going to code this feature?

X

Are there any technical decisions made that should be shared?

X

What is preventing us from delivering this feature?

X

What can the feature potentially break?

X

[dosubot]

🤖

Hello,

Thank you for your detailed request. Based on the context provided, I understand that you're looking to add a new collection type to the Quivr repository. Here's how you can go about it:

To add a new collection type in the Quivr codebase, you need to define a new interface that extends the Schema.CollectionType interface. This interface should include the following properties:

• collectionName: A string that represents the name of the collection.
• info: An object that includes metadata about the collection, such as its singular name, plural name, and display name.
• options: An object that specifies whether the collection supports draft and publish functionality.
• attributes: An object that defines the attributes of the collection. Each attribute should be an instance of the Attribute type, and it can include various modifiers such as Required, Private, and Relation.

Here is an example of how you can add a new collection type:

export interface NewCollectionType extends Schema.CollectionType {
  collectionName: 'new_collection';
  info: {
    singularName: 'new-collection';
    pluralName: 'new-collections';
    displayName: 'New Collection';
  };
  options: {
    draftAndPublish: true;
  };
  attributes: {
    attribute1: Attribute.String &
      Attribute.Required;
    attribute2: Attribute.Number;
    // Add more attributes as needed...
  };
}

This code defines a new collection type named NewCollectionType with two attributes: attribute1 and attribute2. The attribute1 is a required string, and attribute2 is a number. The new collection supports draft and publish functionality.

In the context shared, the pluginOptions property is not used, and instead, an options property is used to specify whether the collection supports draft and publish functionality. Also, the info object does not include a name or description property, and the attributes object does not use the SetMinMaxLength, DefaultTo, Unique, or Relation modifiers. The attributes object also includes a type property for each attribute, and for the image attribute, it includes an allowedTypes property that specifies the types of media that can be uploaded, and a multiple property that specifies whether multiple media files can be uploaded.

You can refer to the following files for more context:

• cms/quivr/types/generated/contentTypes.d.ts
• cms/quivr/src/api/use-case/content-types/use-case/schema.json

I hope this helps! If you have any more questions or need further clarification, feel free to ask.

Best,
Dosu

Sources

• [File]
• [Backend Architecture Refacto]
• [Epic]
• cms/quivr/Dockerfile
• cms/quivr/src/api/use-case/content-types/use-case/schema.json
• cms/quivr/types/generated/contentTypes.d.ts

---

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

[github-actions]

Thanks for your contributions, we'll be closing this issue as it has gone stale. Feel free to reopen if you'd like to continue the discussion.

[github-actions]

Thanks for your contributions, we'll be closing this issue as it has gone stale. Feel free to reopen if you'd like to continue the discussion.