We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently a recompute will create all new revisions, even if the recomputing is the same.
Their is a 'dirty' fix to use ems:env:reindex preview --reload-date, but this only works for an environment.
ems:env:reindex preview --reload-date
Suggestion: the recompute command should get a new option 'changed' for only making new revisions if something changed
Why the naming of 'changed', the ems:contenttype:migration also has an changed option
The text was updated successfully, but these errors were encountered:
Davidmattei
Successfully merging a pull request may close this issue.
Currently a recompute will create all new revisions, even if the recomputing is the same.
Their is a 'dirty' fix to use
ems:env:reindex preview --reload-date, but this only works for an environment.Suggestion: the recompute command should get a new option 'changed' for only making new revisions if something changed
Why the naming of 'changed', the ems:contenttype:migration also has an changed option
The text was updated successfully, but these errors were encountered: