Fix DX types imported from tarball do not have valid ids #2437
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the issue/feature this PR addresses
This Pull Request ensures that DX content types imported from tarball have a valid id.
The id for DX content types imported from tarball is not generated automatically, but keep the original UID as the id. No valid id is generated and therefore not properly catalog, cause the
api.is_temporary(obj)returns FalseCurrent behavior before PR
DX content types imported from tarball do not have a valid id, but keep original UID as the id
Desired behavior after PR is merged
DX content types imported from tarball have a valid id and they are properly catalogued
--
I confirm I have tested this PR thoroughly and coded it according to PEP8
and Plone's Python styleguide standards.