Closed (fixed)
Project:
Field Group
Version:
4.x-dev
Component:
Miscellaneous
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Sep 2023 at 13:05 UTC
Updated:
13 May 2026 at 08:30 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
anybodyComment #5
elberComment #6
elberHi please revise
Comment #8
rajdip_755Comment #9
tirupati_singh commentedHi, I've applied both the
MR !39andMR !38as patches and got error while applying the patches. I think it has occurred due to the presence of merge conflicts on both the MRs. I've reviewed both the MRs and found that theMR !38only changes the doc comments@param typefor only 3 files and theMR !39has updated both doc comments and parameter name as per the@param typefor all the file wherever it has been used. I think MR! 39 has the appropriate changes for the raised issue and MR !38 has only few changes, so MR !38 can be closed for now.I've tested the changes made on MR !39 by checking out the
3387046-revise-rendering-objectbranch and the module functionlality is working fine. Got no errors while using the module. I've attached the screenshots for reference.As there's merge error/conflicts present for MR !39 and few changes still required, hence changing the issue status to Needs work.
@rajdip_755, I've left comments on MR !39 please have a look.
Comment #10
rajdip_755Thanks @Tirupati_Singh for reviewing the MR.
I've updated the MR as per the changes requested. Please review the updated MR.
Comment #11
tirupati_singh commentedI've tested the changes made on MR !39 and can confirm that the issue has been resolved successfully. I'm attaching the screenshots for reference. Hence moving the status to RTBC.
Comment #13
anybodyComment #14
anybodyComment #15
anybodyPpeline is failing!
Comment #16
anybodyComment #17
benstallings commentedThe MR has a merge conflict with the 4.x branch.
Comment #18
benstallings commentedComment #19
benstallings commentedComment #20
anybodyThanks @benstallings LGTM. I just left one comment, think we should remove the CHANGELOG entirely. Doesn't HAVE to be done here, but we should do it IMHO.
Comment #22
anybody