Using mappings in widget.js

[Nizzan943]

Hey!
First of all, sorry if it's a stupid question, but I have almost 0 knowledge in frontend architecture and JS.
I'm working on integration with Azure to be able to see the number of PRs open I have in a specific repository, and I need to take a value from service.yaml, from a widget and use it to filter the HTTP response result and look for objects with the same string values.
use case:
widget.js

import credentialedProxyHandler from "utils/proxy/handlers/credentialed";

const widget = {
  api: "https://dev.azure.com/{organization}/{project}/_apis/git/repositories/{repositoryId}/pullrequests?{params}",
  proxyHandler: credentialedProxyHandler,

  mappings: {
    totalPrs: {
      endpoint: "totalPrs",
    },
    myPrs: {
      endpoint: "searchCriteria.creatorId={creatorId}",
      params: "searchCriteria.creatorId={creatorId}"
    }
  }
};

export default widget;

I'm not sure I understood how to fully use mappings object, I tried to look on other widgets but cant make it work.
technically, mapping.totalPrs is not needed, because the API without any parameters will give me the total PR for the repository. but if I'm not set this object I get "Unsupported service endpoint", also it seems to have a mapping object without endpoint lead also to "Unsupported service endpoint".

What I want

I want to have 2 API requests.

1. "https://dev.azure.com/{organization}/{project}/_apis/git/repositories/{repositoryId}/pullrequests to get all PRs for repository.
   2. https://dev.azure.com/{organization}/{project}/_apis/git/repositories/{repositoryId}/pullrequests?searchCriteria.creatorId={creatorId} to get all PRs for specific user.

How can I achieve that without damaging homepage proxy architecture?
Cheers!

[Nizzan943]

@shamoon pardon, please advise ^_^

[shamoon]

We dont need two separate azure widgets, thats not an acceptable solution.

I havent looked at this yet but did you try something like? "https://dev.azure.com/{organization}/{project}/_apis/git/repositories/{repositoryId}/{endpoint}"

and then one is endpoint: pullrequests
and the other endpoint: pullrequests?searchCriteria.creatorId={creatorId}

Or theres another way around this, but again, not two separate widgets

[github-actions[bot]]

This discussion has been automatically closed due to inactivity.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.