Skip to content

feat: Chat, Step, Steps, RatingInput components#271

Merged
ramedina86 merged 36 commits intodevfrom
feature-chat
Mar 1, 2024
Merged

feat: Chat, Step, Steps, RatingInput components#271
ramedina86 merged 36 commits intodevfrom
feature-chat

Conversation

@ramedina86
Copy link
Collaborator

No description provided.

@ramedina86 ramedina86 changed the base branch from master to dev February 29, 2024 13:32
@ramedina86 ramedina86 marked this pull request as draft February 29, 2024 13:38
@ramedina86 ramedina86 marked this pull request as ready for review February 29, 2024 21:24
@ramedina86 ramedina86 requested a review from raaymax February 29, 2024 21:24
@ramedina86
Copy link
Collaborator Author

ramedina86 commented Feb 29, 2024

@raaymax Can you help me by reviewing this one?

No need to look at every line of code but I'd appreciate your input when it comes to standards, e.g. conventional commits. Am I using these correctly?

Apologies for the big PR.

Comment on lines 49 to 52
import CoreChat from "../core_components/content/CoreChat.vue";
import CoreStep from "../core_components/layout/CoreStep.vue";
import CoreSteps from "../core_components/layout/CoreSteps.vue";
import CoreRating from "../core_components/input/CoreRatingInput.vue";
Copy link
Collaborator

Choose a reason for hiding this comment

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

suggestion(non-blocking): All imports are sorted by folder currently, we can sort them further or just remove comments from above.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Thanks, I'll sort it.

I used to be part of a team that had a linting rule (I think it was a linting rule) that automatically applied alphabetical order to imports. What are your thoughts? Is this worth it?

Comment on lines +159 to +163
incomingInitials: {
name: "Incoming initials",
default: "AI",
type: FieldType.Text,
},
Copy link
Collaborator

Choose a reason for hiding this comment

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

question: shouldn't this come from message?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

In a normal chat, absolutely. But since this is in fact a component to create chatbots, it's expected that it'll always be the same entity. "AI" or for example if you want to create a "Coding Companion", "CC".

Not requiring this also allows you to simply pass a string for the response which is nice.

Perhaps the question is, should this component be named "chatbot" instead?

@raaymax
Copy link
Collaborator

raaymax commented Mar 1, 2024

Generally about conventional commits it's totally up to us whats valid but generally it's just prefix(scope): message where scope is optional. You can also mark commit as "breaking change" with ! for example feat(core)!: state synchronization is replaced by event stream
release-please is parsing whole commits history and based on that it will generate changelog and release message.
Most important for this tool are feat and fix prefixes because only those will be visible. The rest are ignored.

@ramedina86 ramedina86 merged commit d295165 into dev Mar 1, 2024
@ramedina86 ramedina86 deleted the feature-chat branch March 6, 2024 12:27
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