Replaced the "or" condition with "and" condition . "||"->"&&" to solve "CHAT-HISTORY-BUTTON" visiblity bug .

[SwamiDewalkarVWITS]

Purpose

Replaced the "or" condition with "and" condition . "||"->"&&" to solve "CHAT-HISTORY-BUTTON" visiblity bug .

even if showChatHistoryBrowser is False & showChatHistoryCosmos is True , the fronted was showing the "open-chat-history-button"

Does this introduce a breaking change?

When developers merge from main and run the server, azd up, or azd deploy, will this produce an error?
If you're not sure, try it out on an old environment.

[ ] Yes
[✓] No

Does this require changes to learn.microsoft.com docs?

This repository is referenced by this tutorial
which includes deployment, settings and usage instructions. If text or screenshot need to change in the tutorial,
check the box below and notify the tutorial author. A Microsoft employee can do this for you if you're an external contributor.

[ ] Yes
[✓] No

Type of change

[✓] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

Code quality checklist

See CONTRIBUTING.md for more details.

• [✓] The current tests all pass (python -m pytest).
• [✓] I added tests that prove my fix is effective or that my feature works
• [✓] I ran python -m pytest --cov to verify 100% coverage of added lines
• [✓] I ran python -m mypy to check for type errors
• [✓] I either used the pre-commit hooks or ran ruff and black manually on my code.

[pamelafox]

Hm, I'm confused. If showChatHistoryCosmos is true, wouldn't you want to see the chat history? We should be showing the chat history if the app is either using chat history with CosmosDB for logged in users, or if the app is using chat history with indexedDB for non-logged in users.