Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat: update about refreshing page after CRUD & mark-up about notification channel #5221

Conversation

seungyeoneeee
Copy link
Contributor

To Reviewers

  • Self-reviewed (coding conventions, bug-free, functionality verified, tests checked, documentation updated)
  • Minor change, review optional (style, chore, ci, straightforward changes, etc.)
  • Previously reviewed in feature branch, no further review needed
  • Need review or discussion

Description (optional)

  • update about refreshing page after CRUD
  • mark-up (notification channel modals)

Things to Talk About (optional)

Copy link

vercel bot commented Dec 16, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments
Name Status Preview Comments Updated (UTC)
bye-bye-vuex ⬜️ Ignored (Inspect) Visit Preview Dec 16, 2024 9:09am
dashboard ⬜️ Ignored (Inspect) Visit Preview Dec 16, 2024 9:09am
hotfix2 ⬜️ Ignored (Inspect) Visit Preview Dec 16, 2024 9:09am

Copy link

vercel bot commented Dec 16, 2024

Deployment failed with the following error:

Preview deployments are disabled for this project.

Copy link
Member

@skdud4659 skdud4659 left a comment

Choose a reason for hiding this comment

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

I left some comments!

{ name: 'description', label: 'Description' },
{ name: 'notification', label: 'Notification' },
{ name: 'notification_channel', label: 'Notification Channel' }, // TODO: 따로 가져오기...
Copy link
Member

Choose a reason for hiding this comment

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

👀: It would be nice if comments were written in English, even if it's just a few.

import { assetUrlConverter } from '@/lib/helper/asset-helper';

// Temporary values
const state = reactive({
channelList: [
{
icon: 'ic_notification-protocol_envelope',
label: 'email',
label: i18n.t('IAM.USER_GROUP.MODAL.CREATE_CHANNEL.LIST.EMAIL'),
Copy link
Member

Choose a reason for hiding this comment

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

👀: Is this temporary data, and you even applied translations to it..? Is it going to be removed later?


import { blue } from '@/styles/colors';

const state = reactive({
Copy link
Member

Choose a reason for hiding this comment

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

🤔: Last time, I created a component in the Alert Manager v2 folder. Can't we use that? If it's usable, I think it would be great to turn it into a common component for reuse.

menuItems: MenuItem[]
}

const state = reactive({
Copy link
Member

Choose a reason for hiding this comment

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

🤔: This looks like the same component as the one in Alert Manager v2. Could we make it into a reusable component?

Comment on lines 149 to 155
:deep(.p-text-input) {
width: 100%;
}

:deep(.p-select-dropdown) {
width: 100%;
}
Copy link
Member

Choose a reason for hiding this comment

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

🤔: It would be best to minimize the use of deep in Mirinae as much as possible, and if customization is necessary, it would be good to add the item to Notion so it can be discussed during the Mirinae scrum.
Additionally, when we customize Mirinae components, we add comments like /* custom design-system component - p-context-menu */ so we can track and verify changes if the component gets updated later.

title: '',
themeColor: 'Primary',
type: USER_GROUP_MODAL_TYPE.CREATE_NOTIFICATIONS_FIRST,
title: 'Create Notifications',
Copy link
Member

Choose a reason for hiding this comment

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

👀: Is it okay without the translation?

@@ -28,14 +28,13 @@ const state = reactive({
});

/* Component */
const handleConfirm = () => {
const handleConfirm = async () => {
const deletePromises = storeState.selectedUserGroupIds.map((userGroupId) => fetchDeleteUserGroup({
Copy link
Member

Choose a reason for hiding this comment

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

👀: Is it okay not to use await?

Copy link
Member

@skdud4659 skdud4659 left a comment

Choose a reason for hiding this comment

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

LGTM!
However, I hope the code for the user dropdown is merged after further discussion on Slack!

const state = reactive({
userMode: computed<MenuItem[]>(() => [{
label: i18n.t('IAM.USER_GROUP.MODAL.CREATE_CHANNEL.DESC.USER_MODE.ALL_MEMBERS'),
name: 'allMembers',
Copy link
Member

Choose a reason for hiding this comment

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

👀: How about managing it as a constant to prevent human error?

@seungyeoneeee seungyeoneeee merged commit fb79781 into cloudforet-io:feature-project-alert-manager Dec 16, 2024
4 of 9 checks passed
@seungyeoneeee seungyeoneeee deleted the feature/alert-iam-ug-channel branch December 16, 2024 09:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants