Please put the method colors back.

[Willianwg]

I think that this new way, with the methods all written in gray make the visualization worse. The colors used to facilitate the identification of the requests, now it is difficult to find when you have a lot of tabs. The previous version was more intuitive.

[renjinsk]

Yes please! :)

[fleetimee]

can't differentiate when everything is grey.
the hell they're thinking.

[LordGhapa]

thought it was a bug and tried to see the devtools to fix it

[k3rielit]

Inspired by this, I made a mostly POC Insomnia plugin: https://github.com/k3rielit/insomnia-plugin-recolor
Right now it works, but won't recolor already colored items if you change the http method.

If the problem won't have an official fix soon, I might turn it into a properly working plugin. I couldn't find any good actions to hook, so it functions as a classic userscript, maybe I should use event listeners instead.

[LordGhapa]

nice ,tomorrow I was going to search about , about an official solution it looks like it was going to have it today but git push failed the tests

[LordGhapa]

XD if you use var(--something) everything stops working

const observer = new MutationObserver((mutationList, observer) => {
  const element = document.querySelectorAll('.w-10.flex-shrink-0')
  element.forEach(el => {
    el.style.fontSize = '.85rem'
    el.style.border = 'none'
    el.style.fontWeight = 'bold'

    let text = el.textContent

    switch (text) {
      case 'GET':
        el.style.color = 'rgb(168, 150, 255)'
        break
      case 'POST':
        el.style.color = 'rgb(126, 207, 43)'
        break
      case 'PUT':
        el.style.color = 'rgb(255, 154, 31)'
        break
      case 'PTCH':
        el.style.color = 'rgb(240, 225, 55)'
        break
      case 'DEL':
        el.style.color = 'rgb(255, 86, 49)'
        break
      case 'WS':
        el.style.color = 'rgb(240, 225, 55)'
        break
      default:
        el.style.color = 'rgb(70, 193, 230)'
    }
  })
})

observer.observe(document.body, {
  attributes: true,
  childList: true,
  subtree: true
})

[k3rielit]

I finally figured it out. Instead of processing each span once, or everything at certain intervals, the main observer does the styling once on each span, and attaches another observer to them, looking for changes in its childNode (text), which should be a lot faster, than querying constantly. Loading times, adding/modifying requests are instant.

Also, I'm not a node module/package.json expert, so that part is a bit garbage/userscript like, but at least it works...

( https://github.com/k3rielit/insomnia-plugin-recolor )

[LordGhapa]

I can't judge other people's code, after all I'm a beginner in JS, working without creating problems with memory is enough for me, this is an interesting way of using objects and for the first time I saw "new MutationObserver", watching the childNode looks better than watching the body

[k3rielit]

This bothers me as well. The font is too small, thin, and lost its color, so it's hard to identify the http method at a glance. This was such an unnecessary change.

I'm tempted to switch back to Postman just because of these updates. First the request ordering was broken, and now the UI just got worse. GraphQL requests tend to get stuck. And sometimes between versions it forgets that I had collections and requests, blaming sth about an OpenAPI spec, and I had to write a tool to automatically back up my progress, clear Insomnia's data, and load it back.

I see over 500 issues, and yet the priority is randomly changing styling and injecting AI into yet another simple tool...

[subnetmarco]

I believe this has been addressed, are you finding the colors to be better now?