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
Filter/Where as a standalone concept #5957
Comments
Really looking forward to this! The only way around the |
@RAW4RMCS Currently, these can be imported from See: https://loopback.io/doc/en/lb4/apidocs.repository.filter.html |
@achrinza hmm maybe this isn't the fix for the issue i'm currenly facing if i understand your response correctly, I'm using Nswag for generating a frontend client to consume the api endpoints based on the openapi spec, Example of the generated code base on a controller + model;
As shown here in the function the filter has a Do you recommend a client generator for Loopback where this issue doesn't occur? |
@RAW4RMCS Based on the code, the filter is considered optional, hence the The filter shown on the Swagger UI is auto-generated by Swagger UI itself. Also, it seems to be a limitation of nswag to use an A popular OAS3 generator would be https://github.com/OpenAPITools/openapi-generator. However, I've not tried any of the generators myself. |
see: loopbackio#5957 Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
see: loopbackio#5957 Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
see: loopbackio#5957 Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
see: loopbackio#5957 Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
see: loopbackio#5957 Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
see: loopbackio#5957 Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
see: #5957 Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
Refactor the current implementation of LoopBack's Filter to allow other packages to leverage the filtering implementation and/or support LoopBack's Filter syntax.
The syntax of Filter/Where objects should be well defined and properly documented, to allow 3rd-party implementations to understand all possible values.
There should be TypeScript typings describing Filter, Where, etc., these typings must be accessible independently on
@loopback/repository
(e.g. via a new package).The implementation used by our memory connector should be refactored/extracted into a package that can be used independently from juggler (something like https://www.npmjs.com/package/loopback-filters). It's important to update the connector to use that new package, to ensure there is only single reference implementation.
Nice to have:
The text was updated successfully, but these errors were encountered: