Enter the query into the form above.
API method:
GET /api/symbols?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel search send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
Build the given package, applying all of PHASES in order.
Write an assignment of VALUE to KEY to PORT.
VALUE must be a string (without any special characters such as quotes), a boolean or an integer. Lists are currently not supported
Write a section header for a section named SECTION-NAME to PORT.
Write the assignments in ALIST, an association list, to PORT.
Build the given JavaScript package, applying all of PHASES in order.
Build the given Mix package, applying all of PHASES in order.
Like `delete-dependencies/except' but only acting on development dependencies.
Provides a lambda to supply to modify-json which deletes the specified `fields` which is a list of field-paths as mentioned in `modify-json-fields`. Examples: (delete-fields '( ("path" "to" "field") "path.to.other.field"))
Return a procedure to supply to `modify-json' which modifies the specified JSON file. FIELDS is a list procedure-specific data structures which should include the definition of a ``field-path'' in one of two syntaxes: dot-syntax string such as "devDependencies.esbuild", or a list of strings such as (list "devDependencies" "esbuild").
FIELD-MODIFIER is a procedure called with three arguments: 1) the original field-path, e.g. "dependencies.typescript", 2) the field's surrounding (parent) JSON data, as an association list, and 3) the field name (key), e.g. "typescript". The value it returns should be the modified JSON data associated with the field; in other words, returning the second argument without changing it is a no-op.
FIELD-PATH-MAPPER is a procedure which instructs where the field-path is located within the field structure. INSERT? allows the creation of the field and any missing intermediate fields, while STRICT? causes an error to be thrown if the exact field-path is not found in the data.
Rewrite 'package.json' to allow the build to proceed without packages listed in 'dependencies-to-remove', a list of strings naming npm packages. To negate its effect, and keep DEPENDENCIES-TO-REMOVE instead of removing them, set NEGATE? to #t. DEPENDENCY-KEYS can be used to adjust which dependency fields are targeted.
To prevent the deleted dependencies from being reintroduced, use this function only after the 'patch-dependencies' phase.
Provide package.json modifying callbacks such as (delete-dependencies ...)
Like 'with-atomic-file-replacement', but PROC is called with a single argument---the result of parsing FILE's contents as JSON---and should produce a value to be written as JSON to the replacement FILE.
Like `delete-dependencies', but deleting all dependencies except those listed in DEPENDENCIES-TO-PRESERVE.
Like `replace-fields', but can insert new fields as well.
Provides a lambda to supply to modify-json which replaces the value of the supplied field. `fields` is a list of pairs, where the first element is the field-path and the second element is the value to replace the target with. Examples: (replace-fields '( (("path" "to" "field") "new field value") ("path.to.other.field" "new field value")))
Build the given package, applying all of PHASES in order.