Skip to content
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

Add a new "Clear Entries" button at the top of Telescope #1087

Merged
merged 2 commits into from Jul 8, 2021
Merged

Add a new "Clear Entries" button at the top of Telescope #1087

merged 2 commits into from Jul 8, 2021

Conversation

AlexDanault
Copy link
Contributor

@AlexDanault AlexDanault commented Jul 8, 2021

This pull request adds a new "Clear Entries" button at the top of the layout (after the Pause Recording button).

Clicking it triggers a call the the backend which clears the entries in the database and also wipes the current in-memory entries of the Vue app.

The SVG icon comes from zondicons to match the other telescope icons.

This feature has been touroughly tested and works both when new entries are loaded automatically and when they are not.

Any comments, questions, code review, bugs of missing features would be very welcome.

Personally, as a heavy telescope user, this would be a very welcome feature, and a nice addition to the great tool that telescope is.

When debuging, this new button is much quicker than having to leave your curren window (telescope), go the terminal, call artisan telescope:clear, go back to telescope and refresh the window.

Thanks !

@taylorotwell taylorotwell merged commit c0659a8 into laravel:master Jul 8, 2021
@taylorotwell
Copy link
Member

Merged. Added confirmation - reloaded page entirely instead of managing state in JS.

@AlexDanault
Copy link
Contributor Author

Thanks a lot Taylor !

@emargareten
Copy link
Contributor

@AlexDanault Why didn't this go to branch 4.x?

@AlexDanault
Copy link
Contributor Author

@emargareten At first I was thinking this is a new feature so I followed the doc and used master, but now I realise that it is fully backward compatible and should have gone on 4.x .

Maybe @taylorotwell can move it to 4.x so we get this cool feature sooner ?

@driesvints
Copy link
Member

@AlexDanault Yes feel free to send to 4.x

@AlexDanault
Copy link
Contributor Author

Done, see #1091 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants