Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I added support for 'entity_id' as an alternative to 'user_id' in various endpoints, improved the handling of the 'DEBUG_RAG_API' environment variable, and updated the VSCode launch settings to include an 'envFile' configuration.
entity_id
as an alternative parameter in the/query
,/embed
,/embed-upload
, and/local/embed
endpoints to allow authorization usingentity_id
for shared resources.debug_mode
environment variable handling by ensuring consistent parsing of boolean values, supporting multiple truthy values like'true'
,'1'
,'yes'
, etc.launch.json
to includeenvFile
configuration, allowing environment variables to be loaded during debugging sessions.Change Type
Testing
I tested the changes by running the API locally and invoking the updated endpoints with and without
entity_id
anduser_id
to verify that authorization works correctly. I tested differentDEBUG_RAG_API
values to ensure the debug mode setting is properly handled. I also ran the application in VSCode to confirm that theenvFile
configuration loads environment variables as expected.Test Configuration:
.env
file during testingChecklist