search

elm / virtual-dom

The foundation of HTML and SVG in Elm.
https://package.elm-lang.org/packages/elm/virtual-dom/latest
BSD 3-Clause "New" or "Revised" License
209 stars 80 forks source link

Shortened strings in debugger aren't helpful #121

Closed gyzerok closed 6 years ago

gyzerok commented 6 years ago

Currently strings get shortened in the debugger which in some scenarios defeat it's purpose.

I use Elm inside React application. There is some data getting passed within flags to Elm and decoded there. To be able to easily see what went wrong within mentioned integration, I came up with idea to use Result String Model as a top level model. I was thinking that in case of decoding error I'll be able to see what went wrong easily. However in the debugger I see this:

screen shot 2018-01-11 at 1 39 31

It would be nice to show strings without shortening them or show tooltip with full content on hover.

In my case I can't render this error on the view because it's content shouldn't be exposed to users.

My setup: Firefox 57, Elm 0.18.

process-bot commented 6 years ago

Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!

Here is what to expect next, and if anyone wants to comment, keep these things in mind.

evancz commented 6 years ago

This is a known issue with the debugger. Tracking it here will not help make it happen (as it is a project that would end up in a larger batch of work that considers UX improvements overall) so I am going to close to make the issue list more focused.

muelli commented 6 years ago

Is there a new place to make people with the skill set, time, and willingness aware of this open issue?

I know Github's bug managing capabilities are rather limited. But it's nice to have an open issue to get notifications on activity and to, e.g. be able to help clarify things if necessary.

evancz commented 6 years ago

I think you made the same comment the other day.

Some projects are very large. For example, this project likely involves a redesign of the UI. So having "the skill set, time, and willingness" are not the only factors involved here. Like I say in Code is the Easy Part, in the Elm world, you have to be in coordination with the core team for huge projects like this to have a chance. So if this project was happening, the author would be in communication with core team members and we'd figure things out together.

I appreciate that not everyone agrees with my outlook or how I manage things, but I hope that has clarified things sufficiently.