Add left-pane file tree view and related templates

[aayushkdev]

fix #1682

tree.webm

Summary/Goals of this change
The goal of this PR is to introduce a collapsible file tree panel in the left pane of the project resource view. This view allows users to explore the project's CodebaseResource in a more user friendly way.

• Clicking the chevron next to a folder toggles a dropdown view of its immediate children in the tree (left pane).

  • If the children have already been fetched, they are simply shown or hidden without making another request.
  • Directories without any children are shown without a chevron and cannot be expanded.
  • This action only affects the left pane and does not update the right pane.

• Clicking the folder name is intended to display the list of that folder’s children in the right pane. (Not yet implemented)

• Clicking on a file is intended to show that individual file’s details or metadata in the right pane. (Not yet implemented)

Note: This pr depends on the parent_path field introduced in #1687. To ensure tests pass and the functionality works, I’ve temporarily duplicated the necessary parts of that change here. These changes will be removed once that pr is merged.

[aayushkdev]

Hey @AyanSinhaMahapatra @tdruez can I have a review of this pr

[tdruez]

@aayushkdev Off to a good start, see my various comments for improvements.

The naming convention needs consistency:
resource_tree, file_tree, file_tree_panel, file-tree, CodebaseResourceTree, codebase_tree, Resource Tree
Let's use CodebaseResourceTree and resource_tree everywhere rather than "file...".

You can start the implementation of the left and right panels rendering.

[aayushkdev]

Hey @tdruez could you review the changes and if possible review #1687 so we can get that merged as the further pr's require it and without that I have to keep adding parent_path value to each pr temporarily

[tdruez]

See my comments for refinements.
Once done with those, you can continue the implementation of

Clicking the folder name is intended to display the list of that folder’s children in the right pane. (Not yet implemented)

Clicking on a file is intended to show that individual file’s details or metadata in the right pane. (Not yet implemented)

[tdruez]

@aayushkdev The current code is fine, you can implement the missing parts before the next review round.

[tdruez]

@aayushkdev What's the status on the right panel functionalities?

[aayushkdev]

@aayushkdev What's the status on the right panel functionalities?

I've completed the basic implementation of the right panel functionality and will create a PR soon. I was waiting for the previous PRs to be approved and merged first, so the Git history remains clean. This way, I won't need to temporarily include parts of the previous code just to make things work, only to remove them later before merging.

[tdruez]

I was waiting for the previous PRs to be approved and merged first, so the Git history remains clean.

The commits are squashed as a single one when the PR is merged. You do not have to worry about the git history.
Also, merging the left panel without the right panel does not make sense, the right panel functionalities should be part of this PR.

[aayushkdev]

okayy sure I

I was waiting for the previous PRs to be approved and merged first, so the Git history remains clean.

The commits are squashed as a single one when the PR is merged. You do not have to worry about the git history. Also, merging the left panel without the right panel does not make sense, the right panel functionalities should be part of this PR.

ah okayy I was thinking about seperate prs for right and left pane but yeah that makes much more sense to do it in a single commit I will do a commit with the right pane soon

[tdruez]

@aayushkdev #1691 and #1776 are now merged. You can merge main in this branch as well.

[aayushkdev]

Hey @tdruez I have pushed the right panel but some tests still fail even though all pass in my system I think it might be a issue with the CI/CD as the tests that fail are unrelated to my code

Screencast_20250728_224440.webm

Things that are currently left to do

• implement search and filtering
• implement optimisations + caching
• polish the ui a bit more
• Add any other suggested changes/features

[tdruez]

I think it might be a issue with the CI/CD as the tests that fail are unrelated to my code

@aayushkdev Could you merge the latest main branch here, the unrelated failire should now be fixed.
Also, what's the latest status here on your progress?

[aayushkdev]

For the past week I have been testing out different ways of filtering/searching and I will be making a commit for the filtering functionality soon

I think it might be a issue with the CI/CD as the tests that fail are unrelated to my code

@aayushkdev Could you merge the latest main branch here, the unrelated failire should now be fixed. Also, what's the latest status here on your progress?

[tdruez]

@aayushkdev you haven't reported progress in a while, anything blocking you?

[aayushkdev]

@aayushkdev you haven't reported progress in a while, anything blocking you?

Currently I have my midsems exams going on thats why havent been that active.

I have added filtering support in my latest commit. but the search and filtering are taking time as I am trying to use the existing search/filtering components for adding these features and the existing component are not designed for htmx (display data without page reloads) so I am trying to adapt these components to support htmx for the codebase_tree view and make sure it still supports the other views which use these components.

[tdruez]

. but the search and filtering are taking time as I am trying to use the existing search/filtering components for adding these features and the existing component are not designed for htmx (display data without page reloads) so I am trying to adapt these components to support htmx for the codebase_tree view and make sure it still supports the other views which use these components.

Ok, I'm suggesting that instead of doing too much here, we focus on having a clean, simple first PR that can be merged and used, and we add the search/filtering an more features in other PRs.

[tdruez]

Please remove all the searching and filtering logic and let's have something that can be merged asap ;)

[tdruez]

Do not use the hardcoded values but the variable instead.

[aayushkdev]

This is related to the filters I'll keep this in mind in my next pr

[aayushkdev]

I think this branch should be ready to merge, it has the basic functionality of the resource tree.