Skip to content

Update fetch.py - #94

Open
siffalo wants to merge 1 commit into
edanalytics:mainfrom
siffalo:feature/fetch_supported_params_by_ref
Open

Update fetch.py#94
siffalo wants to merge 1 commit into
edanalytics:mainfrom
siffalo:feature/fetch_supported_params_by_ref

Conversation

@siffalo

@siffalo siffalo commented Jul 29, 2026

Copy link
Copy Markdown

We at Crocus LLC have a recommended requirement from South Carolina Department of Education to use lightbeam in an application we're developing for them. It's been working well to date, both sending and fetching data. However, when we get into advanced use cases of the Ed-Fi API via lightbeam, it lacks support for resource endpoint fetch/query parameters by reference, only by name. The most critical fetch/query parameter we need at the moment is minChangeVersion, and of course it's a parameter by reference, not by name, for all resource endpoints. So either we shift away from lightbeam in these advanced use cases, we use our own fork of lightbeam (not clear at the moment whether a custom lightbeam deployment would be acceptable at SCDE), or we try to get lightbeam to include support for query parameters by reference. You know your swagger model better than I and my morning with it, so this could probably be optimized, but just getting a suggested code change to you, if you'd consider support for query parameters by reference. With this change, I can use minChangeVersion successfully, and of course all other query parameters by reference.

We at Crocus LLC have a recommended requirement from South Carolina Department of Education to use lightbeam in an application we're developing for them.  It's been working well to date, both sending and fetching data.  However, when we get into advanced use cases of the Ed-Fi API via lightbeam, it lacks support for resource endpoint fetch/query parameters by reference, only by name.  The most critical fetch/query parameter we need at the moment is minChangeVersion, and of course it's a parameter by reference, not by name, for all resource endpoints.  So either we shift away from lightbeam in these advanced use cases, we use our own fork of lightbeam (not clear at the moment whether a custom lightbeam deployment would be acceptable at SCDE), or we try to get lightbeam to include support for query parameters by reference.  You know your swagger model better than I and my morning with it, so this could probably be optimized, but just getting a suggested code change to you, if you'd consider support for query parameters by reference.  With this change, I can use minChangeVersion successfully, and of course all other query parameters by reference.
@snyk-io-us

snyk-io-us Bot commented Jul 29, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant