We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem? Please describe. We have pretty simple API providing OWASP entities data via /api/v1/owasp... endpoints.
/api/v1/owasp...
Describe the solution you'd like In order to guarantee the frontend results to be consistent w/ Nest API the source of data for both must be the same.
The adapter should contain a unified code to support any entity index and take only configuration params like model/index name.
The text was updated successfully, but these errors were encountered:
Here unified can be anything like a model name .
Basically what i understood is ...there will be one adaptor to expose data based on entries ?
@arkid15r
Sorry, something went wrong.
My goal is keep the architecture simple. I'm thinking about some sore of bridge between DRF and Algolia if possible. This is a P3, long-term task.
Ok
No branches or pull requests
Is your feature request related to a problem? Please describe.
We have pretty simple API providing OWASP entities data via
/api/v1/owasp...
endpoints.Describe the solution you'd like
In order to guarantee the frontend results to be consistent w/ Nest API the source of data for both must be the same.
The adapter should contain a unified code to support any entity index and take only configuration params like model/index name.
The text was updated successfully, but these errors were encountered: