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

fix(l-n-b-menu-item): separate LNBMenuItem component #1697

Conversation

piggggggggy
Copy link
Member

To Reviewers

  • Skip (style, chore, ci ONLY)
  • Not that difficult

Type of Change

  • New feature
  • Bug fixes
  • Feature improvement
  • Refactor
  • Others (performance improvement, CI/CD, etc.)

Affects to

  • Packages

    • core-lib
    • mirinae
    • etc
  • Apps

    • storybook
    • web

Checklist

  • Did you check the lint and type?
  • Did you document the changes?
    • Changes in mirinae should be reflected in storybook.
  • Did you test the app after the package changes?

Description

SSIA

  • separated for additional usage of LNB item

@vercel
Copy link

vercel bot commented Aug 29, 2023

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

Name Status Preview Comments Updated (UTC)
console ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 29, 2023 3:28am

Copy link
Member

@yuda110 yuda110 left a comment

Choose a reason for hiding this comment

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

LGTM! Could you share this on Wed?

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~!
i left a question!

Comment on lines +1 to +17
<script setup lang="ts">
import { PDivider } from '@spaceone/design-system';
</script>

<template>
<div class="l-n-b-divider-menu-item">
<p-divider />
</div>
</template>

<style lang="postcss" scoped>
.l-n-b-divider-menu-item {
margin-top: 1.25rem;
margin-bottom: 1.25rem;
height: 0;
}
</style>
Copy link
Member

Choose a reason for hiding this comment

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

Q. Is there a reason for separating components even though there's only one divider?

Copy link
Member Author

@piggggggggy piggggggggy Aug 29, 2023

Choose a reason for hiding this comment

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

There are some cases without clear usage in LNB planning, so I separated this for usage with spec.

@piggggggggy piggggggggy merged commit a9fa67d into cloudforet-io:feature-cost-analysis-enhancement Aug 29, 2023
@piggggggggy piggggggggy deleted the feature-cost-analysis-enhancement branch August 29, 2023 06:32
sulmoJ pushed a commit to sulmoJ/console that referenced this pull request Oct 4, 2023
sulmoJ pushed a commit to sulmoJ/console that referenced this pull request Oct 4, 2023
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.

3 participants