IBX-9446: [BO] Fatal error after non-translatable field added to Content Type #533
+157
−1
Conversation
This file contains hidden or 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
|
…to Content Type - Added testcase
…to Content Type - Cleaned up test
… added to Content Type - Added testcase
… added to Content Type - Cleaned up test
adamwojs
force-pushed
the
IBX-9446_BO_Fatal_error_after_non-translatable_field_added_to_Content_Type
branch
from
8030caf to
94091aa
Compare
|
@vidarl Could you please resolve issues reported by PHPStan ? |
|
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:
This is a fix for a regression caused by the "virtual fields" introduced in 98b7b50
For QA:
See ticket for step-by-step on how to reproduce the problem