Skip to content

Conversation

@leenapthine
Copy link
Collaborator

  • Added a filter box to the 'browse publication' search filter that filters out publications that do not contain a primary file.
  • Added the logic for the filter
  • Styled the checkbox slightly (this will probably want more input from Graham).

@leenapthine leenapthine self-assigned this Nov 28, 2024
Base automatically changed from test to h2.2.22 March 22, 2025 00:44
@ghjensen
Copy link
Collaborator

ghjensen commented Jul 11, 2025

Sorry, @pauravhp, quick wording request (before we move out of the review phase): could we please change the wording to "Only show publications with attachments"? I wonder if that might be easier for most people to understand than the current wording.

Copy link
Collaborator

@dleske dleske left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks okay to me. I note that <? $x ?> can be used instead of <?php echo $x ?> but if the full syntax is what's used in the codebase then we should stick with that.

// Run query with limit
$results = $model->entries('list', $filters);

// Lee: Check that publication has an attachment
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is prefixing a comment with the developer's name typical for this codebase?

If we're tagging this code as local modifications, then I would prefer "UVic" or "ARCsoft" as appropriate--git blame can always be used to determine the individual developer.

If this is a reminder to check something again, TODO or TODO(drew): is the way I would go.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've run across some of these comments when browsing through the codebase and it seems like these are just for features. Moving forward if I run across them I will modify them to say ARCsoft or TODO depending on the situation (although many of them are not TODOs I believe). Do you need me to change the highlighted line to ARCsoft?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see any reason to have that or Lee: in this line at all. Please take it out or clarify.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moving forward TODO is appropriate. Actually I should have asked if @ghjensen requested we do this to mark off sections we've modified--is this the case?

If not, I'd say we use TODO if it's a TODO, and otherwise leave out these labels unless/until we have a reason to use them.

@toanhminh0412
Copy link
Collaborator

Looks good to me

@toanhminh0412 toanhminh0412 removed their request for review July 21, 2025 23:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants