Repository navigation
Expose shared query param keys to the front-end #14360
Description
The back-end action and servlet layers either use hard-coded param key values or import from Const.ParamsNames. However, the front-end components all have hard-coded param keys. This increases the risk of mismatched parameter names and inconsistencies between the front and back-end.
We should replace hard-coded param keys to Const.ParamsNames and expose those that are shared with front-end components (i.e. methods that prepare paramsMap before calling the API endpoint) in api-const.ts
Activity
mxms-IP commentedon Jun 29, 2026
Hi, Is anyone working on this issue? Can I pick it up?
[#14360] Expose nextUrl and loginMethod query param keys (#14361)
TobyCyan commentedon Jul 6, 2026
@mxms-IP Hi feel free to open a PR for this! You may also break this issue down and submit smaller PRs if it gets too large.
[#14360] Expose shared query params with FEEDBACK_SESSION prefix (#14376
[#14360] Expose notification query params (#14381)
[#14360] Expose course prefixed query params (#14382)
[#14360] Expose key, searchkey and limit query params (#14389)
[#14360] Expose user and account ID query params (#14383)
[#14360] Expose query logs query params (#14390)
[#14360] Expose Preview query params (#14391)
github-actions commentedon Jul 14, 2026
Help Wanted - Notes for Contributors
This issue is open for contributions from anyone who would like to help.
We do not assign issues to contributors. If you would like to pick up this issue, do post a comment below to express your interest and check if there is anyone else who is already working on the issue. We will do our best to reply and give you the go-ahead, but if we do not, feel free to submit a PR as long as there is no one else working on it.
To get started, do read through our contributing guidelines carefully before making a PR.
If you need any clarifications on our developer guide, or are facing issues that are not found in our troubleshooting guide, please post a message in our discussion forum.
SRamkumar190 commentedon Jul 16, 2026
Hello there! I'd like to work on exposing one of the remaining shared query parameter keys that hasn't been covered by the existing PRs yet. I'll review the merged PRs and submit a small PR using the same pattern.
aishwaryabandapelly-ai commentedon Aug 1, 2026
Hi! I’m a student in the CodePath AI301 program, and I’d like to work on this issue.
I’ll start by reviewing the already merged PRs related to #14360 and identifying the remaining shared query parameter keys that are still hard-coded in the front-end.
My plan is to expose the remaining shared keys through api-const.ts and replace the corresponding hard-coded frontend usages with the shared constants. I’ll try to cover the remaining scope in one PR, but if it becomes too large, I’ll split it into smaller focused PRs following the existing pattern.
I’ll avoid touching params that were already covered by previous PRs or by other contributors.
[TEAMMATES#14360] Fix lint formatting
Lavanya-N24 commentedon Aug 12, 2026
Hi @TobyCyan! I'd like to help expose any remaining shared query parameter keys to
api-const.tsthat haven't been covered by the recent PRs. Could you let me know if there are still specific parameter keys or components left to refactor, or if this issue is already fully covered? Thanks!SamTheSoftwareEngineer commentedon Oct 8, 2026
Hi @TobyCyan ! I'd like to help out on this issue as well for anything that has not already been covered in the previous PRs. Can you inform me if there are still specific components left to refactor, or has this issue been resolved?
Thanks!