# "ClipProjectItem::findItemsMatchingMediaPath" logically belong to the wrong class / or the wrong member modifer is used

**URL:** <https://forums.creativeclouddeveloper.com/t/clipprojectitem-finditemsmatchingmediapath-logically-belong-to-the-wrong-class-or-the-wrong-member-modifer-is-used/12119>\
**Category:** Premiere Pro\
**Tags:** api-feedback\
**Created:** [August 22, 2026, 7:54pm UTC](https://forums.creativeclouddeveloper.com/t/clipprojectitem-finditemsmatchingmediapath-logically-belong-to-the-wrong-class-or-the-wrong-member-modifer-is-used/12119 "2026-08-22T19:54:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MarcClown](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/marcclown/32/4778_2.png) [@MarcClown](https://forums.creativeclouddeveloper.com/u/MarcClown)\
**Post date:** [August 22, 2026, 7:54pm UTC](https://forums.creativeclouddeveloper.com/t/clipprojectitem-finditemsmatchingmediapath-logically-belong-to-the-wrong-class-or-the-wrong-member-modifer-is-used/12119/1 "2026-08-22T19:54:15Z")

</div>

1 –  
`findItemsMatchingMediaPath` being an instance child of `ClipProjectIem` makes so sense.  
Depending on original intent:

- if `findItemsMatchingMediaPath` is supposed to search the whole project → it should be `static` method, not an instance method.  
… So one would write something like:

- if `findItemsMatchingMediaPath` is supposed to find element under the current node (would be most helpful IMO) → it should live under `FolderItem` - since a `ClipProjectItem` cannot have children (technically it could also live on `ProjectItem` but that is a bit confusing - as too broad).  
… So one would write something like:

**But I see no use cases where the API living under ClipProjetItem as instance method would makes sense.**

* * *

2 –  
Also mention in another thread a while back, it make no sense to return a collection of `ProjectItem` since only clip have a `MediaPath` associated with them.  
It should return a collection of `ClipProjectItem`.  
Sure, user could cast each items received, but why the extra headache when it can be fixed in the API ?

* * *

3 – ideally we would have a “Folder” API as well to provide the same capability:

```auto
const project = await ppro.Project.getActiveProject();
const folderItemRoot= await project.getRootItem();
const folderProjectItemList = await folderItemRoot.findMatchingFolder(regex, recurse=true);

```

Many of use probably already have some kind of helper function that simulate that already - but would be a nice convenient API (to avoid everyone to reinvent the wheel).

---

<div class="post-metadata">

**Author:** ![clegleiter](https://avatars.discourse-cdn.com/v4/letter/c/3d9bf3/32.png) [@clegleiter](https://forums.creativeclouddeveloper.com/u/clegleiter)\
**Post date:** [August 25, 2026, 2:36pm UTC](https://forums.creativeclouddeveloper.com/t/clipprojectitem-finditemsmatchingmediapath-logically-belong-to-the-wrong-class-or-the-wrong-member-modifer-is-used/12119/2 "2026-08-25T14:36:47Z")

</div>

Hey @MarcClown ,

It does look like `findItemsMatchingMediaPath` is in the wrong place! I’ve created DVAPR-4267218 on our side to track finding a better home for it.