[GH-ISSUE #2263] [feature]: Set env vars on request link as URL params #781

New issue

Open

opened 2026-03-16 17:11:01 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 17:11:01 +03:00

Owner

Originally created by @leomp12 on GitHub (Apr 13, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2263

Is there an existing issue for this?

I have searched the existing issues

Summary

Support setting fallback value to variables through request link (generated from copy link button) URL params, with something like https://hopp.sh/r/nOWZfsljckVj?env:storeId=1234&env:cartId=5678.

Why should this be worked on?

It would be helpful to share to end users the same request that you are using in development, working on just one Send click without the need to set up environment manually.

Originally created by @leomp12 on GitHub (Apr 13, 2022). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2263 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Summary Support setting fallback value to variables through request link (generated from _copy link_ button) URL params, with something like `https://hopp.sh/r/nOWZfsljckVj?env:storeId=1234&env:cartId=5678`. ### Why should this be worked on? It would be helpful to share to end users the same request that you are using in development, working on just one _Send_ click without the need to set up environment manually.

kerem added the

feature

label

2026-03-16 17:11:01 +03:00

kerem commented

2026-03-16 17:11:12 +03:00

Author

Owner

@leomp12 commented on GitHub (Apr 14, 2022):

And... I can give it a try if you want me to

@leomp12 commented on GitHub (Apr 14, 2022): And... I can give it a try if you want me to

kerem commented

2026-03-16 17:11:18 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Apr 19, 2022):

This is actually a solid idea which we can implement. Our major concerns are more regarding how we will express this through the UX of the app. For example, how will the Environment be represented, will a new environment be created for storing this (how will this work when this link is visited multiple times ?) should it be in Global variables etc. ?

We are looking for suggestions if there are any.

@AndrewBastin commented on GitHub (Apr 19, 2022): This is actually a solid idea which we can implement. Our major concerns are more regarding how we will express this through the UX of the app. For example, how will the Environment be represented, will a new environment be created for storing this (how will this work when this link is visited multiple times ?) should it be in Global variables etc. ? We are looking for suggestions if there are any.

kerem commented

2026-03-16 17:11:23 +03:00

Author

Owner

@leomp12 commented on GitHub (Apr 19, 2022):

Imo it should just set environment variables (global) not set yet.
I mean, in first access to https://hopp.sh/r/nOWZfsljckVj?env:storeId=1234, if user doesn't have storeId global env var, it would be automatically set to 1234, then user may change this value to 5678 and if he accesses the link again nothing would happen with storeId variable, would keep the value 5678.

@leomp12 commented on GitHub (Apr 19, 2022): Imo it should just set environment variables (global) not set yet. I mean, in first access to `https://hopp.sh/r/nOWZfsljckVj?env:storeId=1234`, if user doesn't have `storeId` global env var, it would be automatically set to 1234, then user may change this value to 5678 and if he accesses the link again nothing would happen with `storeId` variable, would keep the value 5678.

kerem referenced this issue

2026-03-17 00:31:22 +03:00

[PR #781] [MERGED] chore(deps): bump yargs-parser from 18.1.2 to 18.1.3 #2853