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(nameguard-react): canonical badge #170

Merged
merged 3 commits into from
Nov 30, 2023

Conversation

notrab
Copy link
Member

@notrab notrab commented Nov 29, 2023

No description provided.

Copy link

This pull request has been linked to Shortcut Story #22894: Implement canonical badge in NameGuard.

Copy link

vercel bot commented Nov 29, 2023

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

Name Status Preview Comments Updated (UTC)
nameguard-website ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 30, 2023 8:23am

Copy link
Member

@lightwalker-eth lightwalker-eth left a comment

Choose a reason for hiding this comment

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

Looks great, thank you !

Copy link
Member

@lightwalker-eth lightwalker-eth left a comment

Choose a reason for hiding this comment

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

Looks good, thank you 👍

@notrab notrab merged commit 43fad09 into main Nov 30, 2023
4 of 5 checks passed
@notrab notrab deleted the notrab/sc-22894/implement-canonical-badge-in-nameguard branch November 30, 2023 08:20
/**
* The canonical status for the current grapheme.
* */
is_canonical: boolean;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is_canoncial is not in ConsolidatedGraphemeGuardReport, we need new type: ConfusableGuardReport extends ConsolidatedGraphemeGuardReport

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