GithubHelp home page GithubHelp logo

Comments (5)

vinijmoura avatar vinijmoura commented on August 17, 2024 1

on body, use keywords file: , ext: , class: etc. on searchText parameter separated by space!

Example:

{
"searchText": "mysearch file:azure-pipelines ext:yml",
"$top": 1000,
"filters": {
"Project": [
"MyProject"
]
}
}

from vsts-rest-api-specs.

YousefImran avatar YousefImran commented on August 17, 2024 1

on body, use keywords file: , ext: , class: etc. on searchText parameter separated by space!

Example:

{ "searchText": "mysearch file:azure-pipelines ext:yml", "$top": 1000, "filters": { "Project": [ "MyProject" ] } }

Unfortunately, I have a lot more questions and I would like to be independent if possible. For example, what query parameters are supported by the endpoint? (I would like to filter some properties out. For example, return only fileName and path). Which parameters are required (I had to discover this by trial and error and to find out the response is limited to 2000 rows/objects with $skip = 1000 and $top = 1000 (as upper ranges)). Is there an endpoint documentation somewhere? Can I discover it in Azure DevOps CLI? Etc. Thanks ahead.

from vsts-rest-api-specs.

YousefImran avatar YousefImran commented on August 17, 2024

Apologies if this is the wrong place, but for the life of me I cannot find the JSON schema for Azure DevOps REST API requests. The documentation includes one sample that is not comprehensive. Mainly, I would like to learn the format of filters to use in the request body to customize my search (such as excluding certain paths).

from vsts-rest-api-specs.

YousefImran avatar YousefImran commented on August 17, 2024

from vsts-rest-api-specs.

vinijmoura avatar vinijmoura commented on August 17, 2024

on body, use keywords file: , ext: , class: etc. on searchText parameter separated by space!
Example:
{ "searchText": "mysearch file:azure-pipelines ext:yml", "$top": 1000, "filters": { "Project": [ "MyProject" ] } }

Unfortunately, I have a lot more questions and I would like to be independent if possible. For example, what query parameters are supported by the endpoint? (I would like to filter some properties out. For example, return only fileName and path). Which parameters are required (I had to discover this by trial and error and to find out the response is limited to 2000 rows/objects with $skip = 1000 and $top = 1000 (as upper ranges)). Is there an endpoint documentation somewhere? Can I discover it in Azure DevOps CLI? Etc. Thanks ahead.

I agree. The documentation is not clear!

from vsts-rest-api-specs.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.