Skip to content

Backend CLI: --mappings-only and --create-only confusing #1781

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.

Sign up for GitHub

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

Jump to bottom
Open
lukavdplas opened this issue Apr 15, 2025 · 0 comments
Open

Backend CLI: --mappings-only and --create-only confusing #1781

lukavdplas opened this issue Apr 15, 2025 · 0 comments
Labels
backend changes to the django backend code quality code & performance improvements that do not affect user functionality

Comments

@lukavdplas
Copy link
Contributor

The index command includes these two flags (among others):

  • --mappings-only: the index job should create an index but not populate it with documents
  • --create-only: the index job should be created but not run

I didn't think of this when I worked on #1759, but --create-only sounds like it means "only create the index", i.e. what --mappings-only does.

This is not ideal; perhaps these flag should be renamed.
@lukavdplas lukavdplas added backend changes to the django backend code quality code & performance improvements that do not affect user functionality labels Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backend changes to the django backend code quality code & performance improvements that do not affect user functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lukavdplas