-
Notifications
You must be signed in to change notification settings - Fork 0
feat: Add option keepUnknownIndexes to retain indexes which are not specified in schema (#9857)
#13
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -25,7 +25,7 @@ export interface SchemaOptions { | |
| /* Is true if Parse Server will reject any attempts to modify the schema while the server is running. | ||
| :DEFAULT: false */ | ||
| lockSchemas: ?boolean; | ||
| /* Keep indexes that are not defined in the schema and are present in the database. Set this to true if you are adding indexes manually so that it wont be dropped when you run schema migration | ||
| /* (Optional) Keep indexes that are present in the database but not defined in the schema. Set this to `true` if you are adding indexes manually, so that they won't be removed when running schema migration. Default is `false`. | ||
| :DEFAULT: false */ | ||
| keepUnknownIndexes: ?boolean; | ||
|
Comment on lines
+28
to
30
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This pull request adds the configuration option |
||
| /* Execute a callback before running schema migrations. */ | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that
ignoreUndefinedhas been moved here to maintain alphabetical order, which is great for readability. This is likely due to the build script that generates this file. To improve consistency and prevent noisy diffs in the future, it would be beneficial to also reorder the properties within theDatabaseOptionsinterface insrc/Options/index.jsto be alphabetical. This would make the source and generated files consistent.