Active/selected environment not visible about insomnia HOT 14 CLOSED

This is a terrible bug and a deal breaker. It is imperative that I don't make post/put requests to production by accident.

from insomnia.

I have to say... I love Insomnia, but 9.3 was one of the worst releases so far. The whole UI is glitch and don't work properly and besides that we have this kind of weird decision of hiding one of the most important information from our sight.

from insomnia.

I really want to stay on Insomina as the alternatives are not great, but bugs/ releases like this make it very hard... It just seems to get progressively worse.

from insomnia.

This is a terrible bug and a deal breaker. It is imperative that I don't make post/put requests to production by accident.

Yes, makes sense. We will bring this back, as it shouldn't have been removed from a product standpoint. This is a regression introduced with the creation of global environment variables, we will make a release by EoW next week to re-introduce it.

from insomnia.

but 9.3 was one of the worst releases so far

It just seems to get progressively worse.

Insomnia is objectively getting better every day, we are shipping new capabilities every month.

Regressions/mistakes happen, Insomnia is a large project at this point, and this one will be fixed this week. I understand the value of seeing immediately the environment variable that's been selected, and we are bringing it back this week.

from insomnia.

Insomnia v9.3.2 has been released fixing this issue.

from insomnia.

I can confirm, that this issue is present in the linux appimage as well.

As you can see from the above there is no visible indicator about which environment is used, you have to click on the "Manage Environments" button to find that out.

It is frustrating to say the least.

I would like to see the environment name at least on the button or next to it!

from insomnia.

This is how it will look like in 9.3.2 when both a global environment, and a collection env, are selected.

We also added counters for cookies and certificates, so it's easier to see if they are being valued or not:

from insomnia.

but 9.3 was one of the worst releases so far

It just seems to get progressively worse.

Insomnia is objectively getting better every day, we are shipping new capabilities every month.

Regressions/mistakes happen, Insomnia is a large project at this point, and this one will be fixed this week. I understand the value of seeing immediately the environment variable that's been selected, and we are bringing it back this week.

I love Insomnia, thx for try to fix this one. As you said, mistakes happen.

from insomnia.

Insomnia is objectively getting better every day, we are shipping new capabilities every month.

That is debatable. I cannot really remember any new feature that was relevant to me. That would be fine if previous/core functionality wasn't removed or broken every release more and more. I used to be very enthusiastic about this app but now the only thing keeping me here are the people I converted into the ecosystem while I was happy with the app. The app used to be simple (which is a huge benefit IMO) alternative to Postman that offered everything I needed to interact with APIs. But then you forced us to create accounts (I don't think it is even possible to import exports from other people without them and even if they have accounts, data import is partially broken for over a year), and you now keep working on shrinking important parts of UI and call it a improvement. There are several people in my team alone who reverted to versions prior to V8 disaster and will never attempt to downgrade to 8 or 9

from insomnia.

Thanks for the feedback, answers below:

You want a new request - you must go to headers and delete "default" entries

We are adding the ability in the Preferences to remove the automatically generated User-Agent header. This header was also added in previous versions of Insomnia since a very long time, but simply we didn't show it in the Headers section (but now we do).

You want to import data - you must go through hundreds of requests to fix broken tags

Let me ask the team if we are aware of this issue.

You want to see docs - make sure to to switch between sections after selecting request

I can replicate, we can fix this for upcoming 9.3.2

You want to delete request - hunt down a dialog to confirm

The confirmation dialog was introduced because - on the other end - many users complained that they lost data by accidentally deleting an entire request. So we decided to prioritize for not losing data, but perhaps we can introduce a "Do not ask again" checkbox so that after the first time we don't ask it again for users that don't mind deleting without a confirmation.

Wanna continue where you have left of?

You mean after restarting the application, the ability to be redirected directly into the last collection that you were working on?

from insomnia.

In the past releases we have stabilized the application significantly although when we build major features (like the new global environments) there is a risk of introducing regressions like the one discussed here, that we promptly fixed and we will ship it soon in 9.3.2 this week. We would rather avoid introducing regressions, but yes it can happen and we will try to fix them asap when it does.

In what ways Insomnia is not simple anymore? You can still go straight into a collection and start debugging as usual. Yes, we require a login because we are running a business, but the usability of the app hasn't changed much over the years and most of the capabilities are free.

from insomnia.

In what ways Insomnia is not simple anymore?

Bunch of actions now require some additional click or workaround:

• You want a new request - you must go to headers and delete "default" entries
• You want to import data - you must go through hundreds of requests to fix broken tags
• You want to see docs - make sure to to switch between sections after selecting request
• You want to delete request - hunt down a dialog to confirm
• Wanna continue where you have left of? - nope
• Wanna update - pray to have app usable after relaunch

In the past releases we have stabilized the application significantly although when we build major features (like the new global environments) there is a risk of introducing regressions like the one discussed here

I am aware that unintentional regressions happen as well, but it is curious how fast I bump into them. I saw this issue less than a minute after starting this version.

Yes, we require a login because we are running a business

I get that you need to farm data these days to be profitable. I have payed for a lot less needed software than this, but not after losing my data after attempting to work after update or being forced to create an account

from insomnia.

Let me ask the team if we are aware of this issue

#6070

You mean after restarting the application, the ability to be redirected directly into the last collection that you were working on?

Exactly: #6928

but perhaps we can introduce a "Do not ask again" checkbox so that after the first time we don't ask it again for users that don't mind deleting without a confirmation

It was a nitpick I bumped in that day. I do not mind it much. Only an example how app requires more clicks and takes up more space but probably not something I would complain about otherwise.

from insomnia.