Opened 7 years ago

Closed 6 years ago

Be able to set the path where search

Reported by: Owned by: guillaumeh rjollos normal RepoSearchPlugin normal 0.11

Description

Hello,

To add in wich list: Possibilty to set the path where search in repository. We have, in my compagny, a very big repository, and if we could set the path where search, it'll safe time ! :)

comment:1 follow-up: ↓ 4 Changed 7 years ago by athomas

• Resolution set to fixed
• Status changed from new to closed

Is the exclude option not sufficient? eg.

[repo-search]
include = /some/path/*


comment:2 Changed 7 years ago by athomas

• Resolution fixed deleted
• Status changed from closed to reopened

comment:3 Changed 7 years ago by athomas

• Resolution set to worksforme
• Status changed from reopened to closed

comment:4 in reply to: ↑ 1 Changed 7 years ago by 7lima

Is the exclude option not sufficient? eg. include = /some/path/*

When I try to include/exclude a path like /trunk/... the plugin does not recognize the path. I had to write it without the leading slash: trunk/....

Maybe that's what caused the ticket to be issued. Wouldn't you think leading slashes should be allowed?

comment:5 Changed 7 years ago by athomas

I'm pretty sure I just do a glob match, so it's likely that Trac's repository paths don't include the leading /. A note to that effect would be useful in the Wiki...

comment:6 Changed 7 years ago by 7lima

I left a note in the Wiki.

comment:7 Changed 7 years ago by anonymous

• Resolution worksforme deleted
• Status changed from closed to reopened

Heu... no, that's not sufficient.

My idear is to be able to set the path where search in the search form. For example, today, I want to search in /project1/ but tomorrow, I need to search in /project2/

And that the same for all of my team.

comment:8 Changed 7 years ago by anonymous

1 month after, no news ? :)

comment:10 Changed 6 years ago by rjollos

• Owner changed from athomas to rjollos
• Status changed from reopened to new

Reassigning ticket after changing maintainer of plugin.

comment:11 Changed 6 years ago by rjollos

• Resolution set to worksforme
• Status changed from new to closed

Seems like we could probably just strip leading slashes from the include and exclude parameters. Since the original issue is solved in this ticket, I have opened another ticket to list this feature as an enhancement. See #6558.