You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create Aspire Starter App with Redis dotnet new aspire-starter --use-redis-cache -o Aspire1
Run the project and navigate to aspire dashboard by clicking the link in CLI dotnet run
Click the cache in Resources page
Hide all the details for Resource, Endpoints, Volumes, Health Checks and Environment variables.
Navigate to other projects in Resources page and go back to cache
ACTUAL
The "Health Check" remained expanded by default after hiding the details.
EXPECTED
The details for "Health Check" should remain hidden just like the other items after hiding it.
The text was updated successfully, but these errors were encountered:
vmykagapuz
changed the title
[WebToolsE2E][Aspire] The details for "Health Check" remained expanded by default after hiding the details.
[WebToolsE2E][Aspire] The details for "Health checks" in Aspire dashboard remained expanded by default after hiding the details.
Nov 21, 2024
vmykagapuz
changed the title
[WebToolsE2E][Aspire] The details for "Health checks" in Aspire dashboard remained expanded by default after hiding the details.
[WebToolsE2E][Aspire] The details for "Health checks" of cache in Resources remained expanded by default after hiding the details.
Nov 21, 2024
vmykagapuz
changed the title
[WebToolsE2E][Aspire] The details for "Health checks" of cache in Resources remained expanded by default after hiding the details.
[WebToolsE2E][Aspire] The "Health checks" of cache in Resources remained expanded by default after hiding the details.
Nov 21, 2024
REFRESSION INFO
INSTALL STEPS
REPRO STEPS
dotnet new aspire-starter --use-redis-cache -o Aspire1
dotnet run
ACTUAL
The "Health Check" remained expanded by default after hiding the details.
EXPECTED
The details for "Health Check" should remain hidden just like the other items after hiding it.
The text was updated successfully, but these errors were encountered: