-
-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix #14562: Resolve error while creating company custom field #14566
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 6.x #14566 +/- ##
============================================
+ Coverage 64.04% 64.07% +0.03%
- Complexity 34670 34677 +7
============================================
Files 2287 2287
Lines 103767 103789 +22
============================================
+ Hits 66453 66503 +50
+ Misses 37314 37286 -28
|
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.
Yes, I faced this issue and this figure out it
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 this is an issue in version 6.x. The changes fix the problem. Looks good to me.
This change requires migration. |
@kuzmany I can see a migration. Does it require another one? |
I have updated the description to execute the migration for the existing setup. He (kuzmany) might be suggesting this. |
@kuzmany can you please explain what you meant by this?
I'd like to clear that up before merge. |
@escopecz it change DB schema for isShortVisible column, then it should be applied as migration to avoid too much diff in schema udpate |
@kuzmany I'm confused. This PR has a migration in it. Please check the diff. Is there any problem with this migration? |
@escopecz ah, my mistake. Sorry. Good to go 👍 |
Description
When creating a custom field for companies, there is an error, and the field is not being created.
Please see this
📋 Steps to test this PR:
For existing setup,