Skip to content

feat(schema): update Tag and Category enums#112

Merged
invisiblemask merged 5 commits intomainfrom
update-tag-category-enums
Mar 17, 2026
Merged

feat(schema): update Tag and Category enums#112
invisiblemask merged 5 commits intomainfrom
update-tag-category-enums

Conversation

@invisiblemask
Copy link
Copy Markdown
Contributor

@invisiblemask invisiblemask commented Mar 16, 2026

Closes https://github.com/EveripediaNetwork/issues/issues/4796 when this PR merged

Summary

  • Reorganized Tag enum into logical groups: People & Teams, Projects & Protocols, Organizations, Cryptoassets, Exchanges & Marketplaces, Events, and Universal Ecosystem Tags
  • Updated Category enum to match the new classification structure with snake_case naming (people_and_teams, projects_and_protocols, organizations, cryptoassets, exchanges_and_marketplaces, events)

Test plan

  • Verify downstream consumers handle the new tag/category values
  • Check that isEventWikiValid still works (the Events tag is preserved)

- Reorganize Tag enum into logical groups (People & Teams, Projects & Protocols,
Organizations, Cryptoassets, Exchanges & Marketplaces, Events, Ecosystem Tags)
and update Category enum to match the new classification structure.
@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Mar 16, 2026

🦋 Changeset detected

Latest commit: 4aa3a97

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@everipedia/iq-utils Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly refines the classification system for entities within the application by restructuring the Tag and Category enums. The changes aim to provide a more granular, logical, and consistent way to categorize various blockchain-related concepts, improving data organization and future extensibility.

Highlights

  • Tag Enum Reorganization: The Tag enum has been comprehensively reorganized into seven distinct logical groups: People & Teams, Projects & Protocols, Organizations, Cryptoassets, Exchanges & Marketplaces, Events, and Universal Ecosystem Tags, introducing many new specific tags and refining existing ones.
  • Category Enum Update: The Category enum was updated to align with the new Tag classification structure, adopting snake_case naming conventions for its values: people_and_teams, projects_and_protocols, organizations, cryptoassets, exchanges_and_marketplaces, and events.
Changelog
  • src/schema/index.ts
    • Reorganized and expanded the Tag enum with new values grouped into logical categories.
    • Updated the Category enum to reflect the new classification structure and naming conventions.
Activity
  • No human activity has been recorded on this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request refactors the Tag and Category enums for better organization and consistency. The changes are generally good, introducing logical grouping for tags and standardized naming for categories. However, I've identified a couple of potential issues. There's a significant inconsistency between the updated Tag enum and the existing LinkedWikiKey enum, which could lead to bugs. Additionally, the Polygon tag, which was previously present, seems to be missing from the new list of ecosystem tags, which might be an oversight.

Copy link
Copy Markdown
Contributor

@Yomzy2223 Yomzy2223 Mar 17, 2026

Choose a reason for hiding this comment

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

Government should be moved to // Organizations section, so that existing tags will be easier to remove later

@@ -117,18 +118,72 @@ export const Tag = z.enum([
"Speakers",
"Stablecoins",
"Venture",
Copy link
Copy Markdown
Contributor

@Yomzy2223 Yomzy2223 Mar 17, 2026

Choose a reason for hiding this comment

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

Venture should be moved to // Organizations section, so that existing tags will be easier to remove later

Copy link
Copy Markdown
Contributor

@Yomzy2223 Yomzy2223 Mar 17, 2026

Choose a reason for hiding this comment

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

Conference should be moved to // Events section

Copy link
Copy Markdown
Contributor

@Yomzy2223 Yomzy2223 Mar 17, 2026

Choose a reason for hiding this comment

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

Hackathon should be moved to // Events section

Copy link
Copy Markdown
Contributor

@Yomzy2223 Yomzy2223 Mar 17, 2026

Choose a reason for hiding this comment

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

Ethereum should be moved to // Universal section

@@ -117,18 +118,72 @@ export const Tag = z.enum([
Copy link
Copy Markdown
Contributor

@Yomzy2223 Yomzy2223 Mar 17, 2026

Choose a reason for hiding this comment

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

Solana should be moved to // Universal section

Copy link
Copy Markdown
Contributor

@Yomzy2223 Yomzy2223 Mar 17, 2026

Choose a reason for hiding this comment

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

Polkadot should be moved to // Universal section

export type EventType = z.infer<typeof EventType>;

export const Tag = z.enum([
// Existing Tags
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We can rename this to // Other Tags since some of the existing tags will now be in the new sections

@invisiblemask invisiblemask merged commit 66e9e24 into main Mar 17, 2026
1 check passed
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