Dotnet-IO-logger / core

Dotnet Input output logger
https://marketplace.visualstudio.com/items?itemName=Diol.diol
MIT License
29 stars 1 forks source link

[Bug] Diol doesn't show logs when run first time #40

Closed OlzhabaevSh closed 3 months ago

OlzhabaevSh commented 5 months ago

Describe the bug If you open Diol the first time, after opening VS and run your application, it is a big chance that you will not see any logs. As far as I understand it happens because an event subscriber starts working only when a User goes to the main page. If a user starts debugging an application before he go to the Diol's main page, you will miss the logs. And then you need to stop and restart your app.

To Reproduce Steps to reproduce the behavior:

  1. Open Diol but don't navigate to the main page.
  2. Open your application in VS
  3. Start debugging
  4. Open Diol and navigate to the main page
  5. Call any http and there are no logs

Expected behavior Diol should show all logs if the extension starts before starting a debugging process, regardless of page where a User is.

Screenshots No need

Additional context We should double focus on UX part of the tool, because there is a big chance that it will be used by dotnet beginners or junior developers who may not know about some "specific" scenarios. In the end they can just think that the tool doesn't work properly.

OlzhabaevSh commented 5 months ago

There are 2 solutions:

  1. We can try to find a place where we subscribe to the logger sender and subscribe in advance (in the welcome page)
  2. We can just remove "welcome" page and navigate a user to the main page from the begining.
OlzhabaevSh commented 5 months ago

I'd prefer the 2nd solution. We need to reorganize navigation in the app and start the app from the main page. Welcome page can be renamed and putted as one of existing tabs. just to have some information about the project. authors, links and etc.

OlzhabaevSh commented 3 months ago

fixed by navigating a user directly to main component