Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fcli * action: Add paging & transformation capabilities to custom request targets #541

Open
rsenden opened this issue May 21, 2024 · 0 comments
Labels
effort:low Easy to implement/fix fcli-actions feature A feature that's on the roadmap or in development prio:medium Medium priority

Comments

@rsenden
Copy link
Contributor

rsenden commented May 21, 2024

The addRequestTargets instruction currently doesn't allow for configuring paging-related functionality or generic input transformations. We should add configuration properties, for example based on SpEL expressions that given a full response (headers, body, ...) can extract the next page URL, or given the full response body, can extract a particular property. For example:

addRequestTargets:
  - name: github
     baseUrl: ...
     headers: ...
     nextPage: ${headers['Link'].next} # Given that this is a composite header, we'd need some easy way to extract the `rel="next"` element
     transform: ${body.data}
@rsenden rsenden added feature A feature that's on the roadmap or in development fcli-actions labels May 21, 2024
@rsenden rsenden added prio:medium Medium priority effort:low Easy to implement/fix labels May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort:low Easy to implement/fix fcli-actions feature A feature that's on the roadmap or in development prio:medium Medium priority
Projects
None yet
Development

No branches or pull requests

1 participant