Apr 3 2024
Apr 2 2024
Mar 1 2024
Cannot reproduce (or I misunderstand the steps):
- Created https://github.com/aklapper/emptyrepository for testing
- Went to phorge.localhost/diffusion/edit/form/default/?vcs=git and created emptyRepo.
- Went to http://phorge.localhost/diffusion/26/uri/edit/208/ and set URI's I/O Type to Read Only
- Went to http://phorge.localhost/diffusion/26/uri/edit/ and set URI to https://github.com/aklapper/emptyrepository and I/O Type to Mirror
- Went to http://phorge.localhost/owners/paths/1/ , edited/removed existing path by setting it to: Include R26 emptyRepo / , and clicked "Save Paths"
Feb 23 2024
Feb 21 2024
The word solution would solve it from the expecting side, you are right. Here in my company the search is used frequently and only as a plain text search. So we have to escape the special regex signs time and again. Just would be interested if this is seen as an issue by others who uses the feature.
We can probably add a checkbox, and some nicer handling for the exception. Or possibly, just adding the word "regex" might solve this from the "user expectation" side.
Thanks for the clarification. I still think we should tackle the exception.
The word "pattern" was meant to imply "regex pattern".
Specifically - the ability to search for a regex is much more useful then a plain-text only search (and costs us basically nothing).
I tried to understand the situation. Thanks.
Feb 14 2024
Feb 12 2024
Feb 9 2024
Jan 28 2024
I have landed my solution.
Jan 25 2024
Jan 19 2024
Jan 18 2024
@bekay while in this area of code would you have any pointers on these other issues I’d like to fix at some point?
- File browse widget doesn’t work unless logged in, for publicly accessible repos
- The search results pop up width is often too narrow to show the full results path, and truncates the end of the path instead of beginning.
@speck @valerio.bozzolan My revision is ready to be tested 😄
Jan 14 2024
Jan 11 2024
Under the hood branches are already supported by the locate feature. The whole file tree is loaded via AJAX, when you first click in the input field. This tree represents the current selected branch.
Jan 4 2024
Dec 9 2023
I’ve been meaning to investigate this. It also has thrown me that it’s not available where you expect it. I do suspect @valerio.bozzolan is right
Dec 8 2023
I wonder if under the hood this means "Add branch support to Locate File"
Well, no opinions from the team. I still think this should be implemented... 😁
Nov 15 2023
Nov 11 2023
Nov 10 2023
Oct 27 2023
you just adopted PHP 7.4 or something similar I think to fix
Thanks for reporting
Nevermind, this is a problem with my setup, sorry for the noise. (I missed the second line, and of course I realized it right after submitting)
Oct 26 2023
Sep 26 2023
Yeah feel free to review D25301
I still like this. Why is this not going forward? 😄
Sep 4 2023
This is now resolved.