-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Saved queries #35
base: master
Are you sure you want to change the base?
Saved queries #35
Conversation
How is this different from #23? |
Also can you provide a picture of what this looks like please? |
Sorry for the late answer, @caleb15. I recorded this short preview so you have an idea how it looks |
Interesting. Are saved queries grouped by each model (queries only appear
on page they are on) or are all queries visible globally? For companies
with a lot of users the amount of saved queries could get quite large.
…On Fri, May 31, 2019, 5:25 AM Vladislav ***@***.***> wrote:
Sorry for the late answer, @caleb15 <https://github.com/caleb15>. I
recorded this short preview so you have an idea how it looks
[image: out]
<https://user-images.githubusercontent.com/1459916/58705137-f2110900-83b6-11e9-9329-794e99a9b9c1.gif>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#35?email_source=notifications&email_token=ALCZY6ILTVIOOJUEW4FGLLDPYEKMHA5CNFSM4GWUGR22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWVCM3Y#issuecomment-497690223>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALCZY6LB3Q36XX7CC5LJGR3PYEKMHANCNFSM4GWUGR2Q>
.
|
Yes, saved queries are grouped by model and displayed only on corresponding pages |
well from a user perspective looks good to me. And you have tests too. Hopefully someone can give you a code review soon. |
Kudos, SonarCloud Quality Gate passed! |
Can we solve the merge request soon as possible? This feature is a need for our company. |
Here is my implemetation for the #1.
Since indicated that DjangoQL can be used separately from the administration interface, I decided to put the urls separately from DjangoQLSearchMixin. JS is also structured accordingly.
I will be glad to hear criticism and suggestions.
Tested with Django 1.8/2.1, Latest Chrome and Mozilla Firefox. I suppose it’s not difficult to support IE9+ after some changes