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.

Sign up for GitHub

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

Jump to bottom

Add support for prefetchData and remote content in CPG cql operations #2618

Open
csandersdev opened this issue Jul 15, 2021 · 1 comment
Open

Add support for prefetchData and remote content in CPG cql operations #2618

csandersdev opened this issue Jul 15, 2021 · 1 comment
Labels
cql P2 Priority 2 - Should Have

Comments

@csandersdev
Copy link
Contributor

Is your feature request related to a problem? Please describe.
The $cql and Library/$evaluate operations implemented in #2577 do not currently support the prefetchData or remote content, data, and endpoint optional input parameters. This ticket is for adding that support.

Describe the solution you'd like
Support the input parameters defined in the operation definitions.

Describe alternatives you've considered
The remote terminology endpoint is already partially supported through the use of the term service configuration in server properties.

Acceptance Criteria
Operations behave in the manner described in the operation definitions.
@csandersdev csandersdev mentioned this issue Jul 15, 2021
Merged
@prb112 prb112 added the cql label Jul 15, 2021
csandersdev added a commit that referenced this issue Dec 7, 2021
@csandersdev
This addresses #3061 first by implementing support for resolving measure
dacf7ec 
references both by resource ID and canonical URL (previously only
canonical URL) and then to also to provide error handling for when the
measure does not properly resolve.

This PR also relates to the missing feature support documented in #2618
not by implementing those features, but by adding error handling that
clearly states to the user those features are not supported at this
time.

Signed-off-by: Corey Sanders <corey.thecolonel@gmail.com>
@csandersdev csandersdev mentioned this issue Dec 7, 2021
Merged
@csandersdev
Copy link
Contributor Author

The initial implementation of this issue ignored these unsupported operation parameters. In #3093, logic was added to warn the user when unsupported operation parameters were used in a request, so that behavior is more clear to the end user. The core issue documented here for adding support is as yet unaddressed. We should leave it open.

@lmsurpre lmsurpre added the P2 Priority 2 - Should Have label Aug 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cql P2 Priority 2 - Should Have
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@prb112 @lmsurpre @csandersdev