# project_panel: Reuse \`index_for_entry\` in \`index_for_selection\` \(\#35034\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/fa788a39a4b8dded19cd27d79c9bd0c63d601039)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: fa788a39a4b8dded19cd27d79c9bd0c63d601039

Requested commit: fa788a39a4b8dded19cd27d79c9bd0c63d601039

Commit: fa788a39a4b8dded19cd27d79c9bd0c63d601039

Tree: 3103d11295eb9f177d7ea8c0eec2ebc357662f5e

Author: Smit Barmase

Committer: GitHub

## Message

```
project_panel: Reuse `index_for_entry` in `index_for_selection` (#35034)

Just refactor I came across while working on another issue.
`index_for_entry` and `index_for_selection` have the exact same logic,
here we can simply reuse `index_for_entry` for `index_for_selection`.

Release Notes:

- N/A
```

## Parents

- [7cdd808db23caa9082b542abbd13b1cace73a501](https://git.cafe/gitcafe/zed/commit/7cdd808db23caa9082b542abbd13b1cace73a501?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/fa788a39a4b8dded19cd27d79c9bd0c63d601039?format=markdown)