Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/software-mansion/live-debugger/discussions/355 below:

What's next? · software-mansion/live-debugger · Discussion #355 · GitHub

Hello, everyone! 👋

We're excited to talk about what's next for LiveDebugger and share our plans with you.

As we continue to enhance and expand LiveDebugger, your feedback is crucial. This tool is made for developers, by developers, and we truly value your input. Whether it's feature suggestions or general improvements, your ideas will help us improve LiveDebugger.

If you think of anything that could help or improve how LiveDebugger works please join this discussion. Let's work together to make LiveDebugger the best tool it can be! 🚀

It was the first release which offered fundamental debugging functionalities such as:

• Rendering LiveComponents tree
• Callback tracing filtered by the LiveComponent/LiveView
• Assigns inspection with live updates
• Listing all LiveView processes
• Showing basic information for the inspected LiveView process

After listening to your comments we are planning to add new features:

• Components Highlighting (to show which LiveComponent/LiveView is being debugged)
• Chrome DevTools extension (it will make debugging sites even easier)
• Dark Mode (with that new color palette for LiveDebugger)
• Filtering callbacks that are being traced
• Nested LiveViews support (it will make debugging complex views easier)

Latest version

• Firefox extension
• View with global callback traces (this view will show all callback traces associated with given LiveViews, we'll add here more filtering options in the future)
• Measuring callback execution time (you will be able to see how long a given callback was executed to find potential bottlenecks)
• Filtering by callback execution time
• Proper way of debugging redirects (currently when a redirect occurs in the debugged application LiveDebugger reloads itself, which forbids debugging callbacks on redirects)

What's planned?

• Major refactor

• Better successor LiveView discovery - this feature improves LiveDebugger’s tracking of LiveView processes when they are replaced due to actions like page reloads or errors, ensuring seamless debugging transitions.

• Inspecting HTML elements - this feature allows users to right-click on an HTML element and choose "inspect LiveElement" to see which LiveView or LiveComponent is responsible for its rendering.

• Search in callback traces - this feature provides a search option that allows users to find specific text phrases within callback traces, enhancing the navigation and analysis of complex data flows.

• Sending custom messages to LiveView/LiveComponent - this feature allows users to manually send customized event messages to specific LiveViews or LiveComponents, similar to using Postman with APIs. This function facilitates testing individual event handlers directly within the LiveDebugger environment.

LiveDebugger (view)

We are also discussing the possibility of officially supporting LiveDebugger in production. We are not sure what consequences it may have in terms of application security yet, but we can see the benefits of using it in a production environment.

For now, LiveDebugger should be used purely as dev only dependency.

If you wanted to write about new features ideas or report some bugs in a more direct way feel free to join LiveDebugger channel in the elixir-lang slack

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4