Fix guild names UI

[bob0005]

User description

Closes #947

---

PR Type

Bug fix, Enhancement

---

Description

• Updated the method for decoding entity names in useEntities.tsx to use shortString.decodeShortString instead of hexToAscii.
• Simplified the getEntityName function call in useGuilds.tsx by removing unnecessary non-null assertion.
• Improved code readability in the formatGuilds function in useGuilds.tsx.

---

Changes walkthrough 📝

	Relevant files
Enhancement	useEntities.tsx Update entity name decoding method to use `shortString`.  client/src/hooks/helpers/useEntities.tsx Removed hexToAscii import. Added shortString import from starknet. Replaced hexToAscii with shortString.decodeShortString for decoding entity names. +3/-3
Bug fix	useGuilds.tsx Simplify guild name retrieval and improve readability.      client/src/hooks/helpers/useGuilds.tsx Simplified getEntityName function call by removing unnecessary non-null assertion. Added spacing for better readability in formatGuilds function. +3/-2

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
eternum	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 17, 2024 9:35am

[github-actions]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review [1-5]	2
🧪 Relevant tests	No
🔒 Security concerns	No
⚡ Key issues to review	Possible Bug: Ensure that shortString.decodeShortString correctly handles all expected input formats and edge cases, as it replaces hexToAscii(numberToHex(Number(entityName.name))). This change in decoding logic could potentially introduce bugs if not all scenarios are covered.
	Refactoring Impact: The removal of the non-null assertion in useGuilds.tsx simplifies the code but ensure that userGuildEntityId is always defined where used, or handle potential undefined cases.

[mentatbot]

The pull request introduces changes that improve code readability and simplify logic. However, careful attention should be given to the new decoding method in useEntities.tsx and the handling of potentially undefined values in useGuilds.tsx to ensure robustness.

Butler is in closed beta. Reply with feedback or to ask Butler to review other parts of the PR. Please give feedback with emoji reacts.

[mentatbot]

Ensure that shortString.decodeShortString correctly handles all expected input formats and edge cases. This change in decoding logic could potentially introduce bugs if not all scenarios are covered.

[mentatbot]

Ensure that userGuildEntityId is always defined where used, or handle potential undefined cases. The removal of the non-null assertion simplifies the code but could lead to undefined behavior if not managed properly.

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Enhancement	Simplify the code by removing redundant BigInt conversion Ensure that userGuildEntityId is always treated as a BigInt by removing the unnecessary conditional check, as it is already converted to BigInt in the new code. client/src/hooks/helpers/useGuilds.tsx [83] -const guildName = userGuildEntityId ? getEntityName(BigInt(userGuildEntityId)) : undefined; +const guildName = userGuildEntityId ? getEntityName(userGuildEntityId) : undefined; Suggestion importance[1-10]: 7 Why: The suggestion correctly identifies that the redundant BigInt conversion can be removed, simplifying the code. However, this is a minor enhancement and does not address a major issue.	7
Maintainability	Remove unnecessary conditional check for better code clarity Remove the unnecessary check for guild_entity_id in the conditional operator since it's already ensured to be non-null by the context. client/src/hooks/helpers/useGuilds.tsx [83] -const guildName = userGuildEntityId ? getEntityName(BigInt(userGuildEntityId)) : undefined; +const guildName = getEntityName(BigInt(userGuildEntityId)); Suggestion importance[1-10]: 6 Why: The suggestion improves code clarity by removing an unnecessary check. However, this is a minor maintainability improvement and does not address a critical issue.	6
Possible issue	Verify the correctness of the shortString.decodeShortString method for decoding entity names Consider checking if shortString module is correctly imported and if decodeShortString method is appropriate for the type of data handled, as the previous implementation used hexToAscii. client/src/hooks/helpers/useEntities.tsx [40] +return entityName ? shortString.decodeShortString(entityName.name.toString()) : entityId.toString(); - Suggestion importance[1-10]: 5 Why: The suggestion raises a valid point about verifying the correctness of the shortString.decodeShortString method. However, it does not provide a concrete improvement or fix, making it more of a cautionary note.	5