Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Save Parameter key and values

See original GitHub issue

I am curious if there is a way to save a query parameters value for later use instead of having to re-enter it each time one goes to the Query Detail page? I only ask because I have not been able to find an answer to that with Google and I do not see anything in the codebase to do it, but maybe I am missing something. Thank you

Issue Analytics

State:
Created a year ago
Comments:7

Top GitHub Comments

1reaction

markswebcommented, Aug 28, 2022

@dwmorrison33 Yeah that sounds like it’d be really useful.

Create a branch from the 1.1.3 tag and when you come to a PR, target this new branch I’ve setup; https://github.com/groveco/django-sql-explorer/tree/release/1.1.4

Then I can do a 1.1.4 release and then, hopefully, merge it to the main branch for it to benefit the users of the latest version as well 👍

0reactions

markswebcommented, Aug 31, 2022

@dwmorrison33 ok, so not having permission is correct.

The workflow for contributing is among the lines of…

fork the repo
clone your fork to your local machine
add the main repo as a remote (this allows you to pull changes in to your fork and base branches from upstream branches like we want here)
create a branch for your contribution and remember to check for guidelines on the repo
once complete and all changes are pushed to your fork github will allow you to create a pull request from the branch.
the PR will be reviewed & merged if accepted