Extenders- Opening a Favorite data set results in a document path temp/_D_/Favorites/dataset(member) - the actual profile name is not included

[travatine]

Hi,

When a "non favorite" data set is opened, the document path is:
temp/_D_/profile name/dataset(member)

This is great as it allows extenders to parse the document path to extract profile and resource name.

However "favorite" data sets result in the profile name of "favorite" instead, e.g.
temp/_D_/favorite/dataset(member)

This makes it impossible to determine which profile was used to open the resource.

Would it be possible to include the profile name in path for favorite data set too?

I think the issue is in the openPS() call to getDocumentFilePath().

export async function openPS(node: IZoweDatasetTreeNode, previewMember: boolean, datasetProvider?: IZoweTree<IZoweDatasetTreeNode>) {
    ...
const documentFilePath = , node);

...

In get document path there is a call to getProfile:

export function getDocumentFilePath(label: string, node: IZoweTreeNode) {
    return path.join(globals.DS_DIR, "/" + getProfile(node) + "/" + appendSuffix(label) );
}

...

The cause of the problem seems to be in getProfile (). The label is used in stead of the profile name.

export function getProfile(node: IZoweTreeNode) {
    let profile = node.getSessionNode().label.trim();
    // if this is a favorite node, further extraction is necessary
    if (profile.includes("[")) {
        profile = profile.substring(profile.indexOf("[") + 1, profile.indexOf("]"));
    }
    return profile;
}

Please would it be possible to use the node getProfileName() function instead?

(That way the path would always include profile name instead of Favorite?)

Thanks.
Travis Thorne.

[venkatzhub]

I would prefer to have an API call to figure out what profile a particular resource belongs to rather than having the extenders parse the document paths.

[github-actions]

Thank you for raising this issue.
The community has 90 days to upvote 👍 the issue.
If it receives 10 upvotes, we will move it to our backlog. If not, we will close it.