Closed (fixed)
Project:
Version Control API
Version:
6.x-2.x-dev
Component:
Views integration
Priority:
Normal
Category:
Feature request
Assigned:
Issue tags:
Reporter:
Created:
25 Jan 2011 at 03:32 UTC
Updated:
15 Apr 2014 at 22:25 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
eliza411 commentedtagging until fixed.
Comment #2
marvil07 commentedOk, I can confirm the bug, but it is not at the parsign level, so it should be a views integration problem, on the joins stuff.
Comment #3
marvil07 commentedHey I think this is ready!
This also modify the commitlog_global_commits default view to use it instead of the current versioncontrol label name views fields, that naturally end up in one row per vc_op_id per label.
Comment #4
sdboyer commentedDoesn't seem to do the trick, at least not with my quick review on staging. Applied the patch, cleared caches and was still seeing one commit per branch.
Comment #5
marvil07 commentedMmm.. I think the problem is that we need to change all views to use it. (maybe you are viewing one that I did not change, are you sure commitlog_global_commits is not working?)
I am now changing all the ones where there are repeated operations, but this is about vc_api, then we need to change vc_git ones and then vc_project ones :-/
Comment #6
marvil07 commentedOk, here the patch changing all the other vc_api views that were not changed.
If this is ok, I will follow with vc_git ones.
Comment #7
marvil07 commentedvc_git related patch for this is on #1043506-1: Use versioncontrol_handler_field_operation_labels views field handler to avoid operation duplicates
Comment #8
marvil07 commentedOk, after fixing a little notice I committed it!