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

Making listing the filtering terms vs using filtering terms more homogeneous #96

Closed
costero-e opened this issue Jun 21, 2023 · 1 comment

Comments

@costero-e
Copy link
Collaborator

Second point of the solution proposed by @mbaudis in #93
In case we are adding an array of the possible scopes for every filtering terms, then we could discuss if we need this, but I guess it would be practical (and necessary) to extend a filteringTerm endpoint for each scope so we can fetch this information by scope. Having to look always at each scope for each object in a "unique" filteringTerm endpoint would become very tedious in my opinion.
If in some models these endpoints can't be filled, then they could go for the generic one and it would still work for every type of beacon.

@costero-e
Copy link
Collaborator Author

Closing issue. See #94

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

No branches or pull requests

1 participant