For the Drupal.org D7 port, we are using extended_file_field for the display of files in an issue node.
We need to add extended_file_field integration into pift if we want to display file status in the issue file table.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 1976074-3.patch | 8.82 KB | jthorson |
| #2 | 1976074-2.patch | 8.8 KB | jthorson |
| #1 | 1976074-1.patch | 3.98 KB | jthorson |
Comments
Comment #1
jthorson commentedStep 1: Basic data integration, with no custom formatters.
Comment #2
jthorson commentedVersion 2: Data integration with custom formatters
Comment #3
jthorson commentedCleanup of the patch from #2 ... this should give us something roughly equivalent with today, except for the css formatting.
Comment #4
jthorson commentedPatch in #3 committed to 7.x-2.x: http://drupalcode.org/project/project_issue_file_test.git/commit/95fff2c...
Leaving open for many further refinements.
Comment #5
dwwMostly looks good on a quick visual inspection. A few minor nits:
+ return l(t('View details'), variable_get('pift_server', 'http://example.com') . 'pifr/test/' . check_plain($test_id));A)
l()already doescheck_plain()on the path, so thecheck_plain()call here (and nearby in the patch) is unnecessary (and in the bizzarre case that$test_idhad an&or something, would lead to double-escaping and brokenness).If
$test_idis always supposed to be an int, you could cast it to an int here if you wanted to be extra careful, but again, not really needed. ;)B) Is the
pift_serversetting supposed to have a trailing slash? Do we enforce that? If it's not defined, this would lead to a URL likehttp://example.compifr/test/1. Seems like we wantvariable_get('pift_server', 'http://example.com') . '/pifr/test/' ...(with a leading slash in front of'/pifr/test/'no?--
The bigger question is how this integration will actually work on d.o -- namely, are we just doing N more columns in the attachments table, or are we trying to do a multi-row thing? If multi-row, how is that going to work? ;) And is any of this being configured on rebuilds (and if so, where)?
Thanks!
-Derek
Comment #6
jthorson commentedCurrently, it's built as columns ... only because that's how I did it before the mockup discussion, and haven't revisited it yet.
As for configuration on rebuilds, I'm thinking this is drupalorg territory ... but to answer your question, it's not happening yet. Baby steps first ... PIFT 7.x-2.x-alpha1 hasn't been merged into bzr yet. ;)
Comment #7
jthorson commenteda) and b) were fixed a while back.
The columns aren't currently being configured on rebuilds; but this configuration also isn't going to exist once the code is refactored to add test results in rows instead of columns.
With that in mind, I'm going to close this off as fixed, since we've actually had basic integration for a number of weeks, and there's no need to artificially inflate the issue counts!
The refactoring of test data into rows instead of columns is also listed as a task in #1979574: Testbot info display on issues, and will be chased there.