Skip to content

Feature/agentic integration#456

Draft
Iguins wants to merge 4 commits intomainfrom
feature/Agentic-integration
Draft

Feature/agentic integration#456
Iguins wants to merge 4 commits intomainfrom
feature/Agentic-integration

Conversation

@Iguins
Copy link
Contributor

@Iguins Iguins commented Oct 27, 2025

GitHub Issue: #

Proposed Changes

  • Bug fix
  • Feature
  • Code style update (formatting)
  • Refactoring (no functional changes, no api changes)
  • Build or CI related changes
  • Documentation content changes
  • Other, please describe:

Description

Recording 2025-05-15 154359

Impact on version

  • Major
    • The template structure was changed.
  • Minor
    • New functionalities were added.
  • Patch
    • A bug in behavior was fixed.
    • Documentation was changed.

PR Checklist

Always applicable

No matter your changes, these checks always apply.

  • Your conventional commits are aligned with the Impact on version section.
  • Updated CHANGELOG.md.
    • Use the latest Major.Minor.X header if you do a Patch change.
    • Create a new Major.Minor.X header if you do a Minor or Major change.
    • If you create a new header, it aligns with the Impact on version section and matches what is generated in the build pipeline.
  • Documentation files were updated according with the changes.
    • Update README.md and TemplateConfig.md if you made changes to templating.
    • Update AzurePipelines.md and APP_README.md if you made changes to pipelines.
    • Update Diagnostics.md if you made changes to diagnostic tools.
    • Update Architecture.md and its diagrams if you made architecture decisions or if you introduced new recipes.
    • ...and so forth: Make sure you update the documentation files associated to the recipes you changed. Review the topics by looking at the content of the doc/ folder.
  • Images about the template are referenced from the wiki and added as images in this git.
  • TODO comments are hints for next steps for users of the template and not planned work.

Contextual

Based on your changes these checks may not apply.

  • Automated tests for the changes have been added/updated.
  • Tested on all relevant platforms

Other information

Internal Issue (If applicable):

x:Name="ChatScrollViewer"
VerticalScrollBarVisibility="Auto"
Padding="16">
<ItemsControl ItemsSource="{Binding Messages}">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's probably best to use ListView instead of ItemsControl for a potentially long list of messages due to virtualization.

@@ -0,0 +1,76 @@
using System;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Agentic" is not a good feature or domain name because it's an adjective. If what you're building is a Chat, name it "Chat" (or "AI Chat"). Having just the word "Agentic" as the domain name is confusing because it could mean multiple things and it forces us to dig into the content to understand that this is actually a chat bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants