Clarification on Route Mappings for Middleware in Knowlg Services #750
Replies: 1 comment
-
@rajnishdargan This issue is part of Knowlg BB, please raise issue in that thread |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello team,
We have recently set up Knowlg and inQuiry services and are looking to integrate the generic editor (upload editor) into our application. Since we don't have a predefined middleware for these services, we're developing our own.
While testing the generic editor from the Sunbird portal, we noticed the following API calls being triggered in the network tab:
We are finding it challenging to understand how these
/action/content/v3/*
or/action/content/v1/*
endpoints map to the routes in the content service. For reference, we are using the routes defined here:https://github.com/Sunbird-Knowlg/knowledge-platform/blob/release-6.0.0/content-api/content-service/conf/routes
In the routes file, we see both /content/v3/* and /content/v4/* paths are available. However, since the endpoints from the generic-editor are predefined and we don't have control over them, we're unsure about a few things:
Should our middleware point
/action/content/v3/*
routes to/content/v3/*
or/content/v4/*
in the backend service?Additionally, where should
/action/content/v1/*
routes point to in the middleware?We couldn't find a direct mapping for content/v1 in the routes file.
We would appreciate any guidance on how to properly configure our middleware to handle these requests.
Thank you for your help!
@pallakartheekreddy @HarishGangula @rajeevsathish @vinukumar-vs @vaibhavbhuva @krgauraw @amitpriyadarshi
@coolbung @itsvick @snehal0904 @arati-tekdi @rushi-tekdi
Beta Was this translation helpful? Give feedback.
All reactions