Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Index fields #7382

Draft
wants to merge 17 commits into
base: main
Choose a base branch
from
Draft

Conversation

demshy
Copy link
Member

@demshy demshy commented Jan 29, 2025

Summary

As described in issue #7381 we need a way to have a specific field set for index files in collections. More info coming as we smooth out the details and clean up the code.

Update March 5th:
Added an option to select path type when adding new entries in such collections. Updated proxy and github backends to work in combination with the new nested system, i18n.

It is ready for some careful internal testing, but there is a ton of stuff still to do:

  • discuss and agree upon the config structure and all the terms used
  • heavy refactoring, according to above
  • updating other backends
  • updating tests
  • update and uncomment path validation
  • test changing index -> single and vice versa

Test plan

Add the following config to the collection options. Pattern is required. Fields are optional, setting them will result in a different entry form for this file. Label is also optional and will add prefix to the title in the entry list.

    index_file: {
      pattern: "^index$",
      fields: [
        ...
      ],
      label: 'Index'
    }

Checklist

Please add a x inside each checkbox:

A picture of a cute animal (not mandatory but encouraged)

@demshy demshy force-pushed the feat/index-fields branch from cb61157 to db6b1b0 Compare February 6, 2025 09:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants