Add uranium-raycast-plugin extension #21501
Conversation
|
Congratulations on your new Raycast extension! 🚀 You can expect an initial review within five business days. Once the PR is approved and merged, the extension will be available on our Store. |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Greptile Summary
This PR adds a new Uranium Raycast extension for NFT management, providing commands to mint assets, create collections, and manage digital assets on the permaweb. The extension integrates with Uranium's API for blockchain operations.
• Core functionality: Well-structured extension with proper React Query and form handling
• API integration: Clean axios setup with proper API key injection
• Configuration: Proper ESLint and Prettier configuration following Raycast standards
• Issues found: Manual Preferences interface definition and missing metadata folder for store submission
Confidence score: 4/5
- This PR is safe to merge with minor issues that need addressing
- The extension is well-structured with good practices, but has two issues: manually defined Preferences interface (syntax fix) and missing metadata folder required for store submission (process requirement)
- src/api/apiClient.ts needs Preferences interface removed, and metadata folder with screenshots needs to be added
Important Files Changed
File Analysis
| Filename | Score | Overview | Issues |
|---|---|---|---|
| extensions/uranium-raycast-plugin/src/api/apiClient.ts | 4/5 | Sets up axios client with API key injection and request handling | Manual Preferences interface definition (should be autogenerated) |
| extensions/uranium-raycast-plugin/src/contracts-create.tsx | 5/5 | Form component for creating NFT collections with validation and limit checks | None identified |
| extensions/uranium-raycast-plugin/package.json | 4/5 | Extension configuration with commands, dependencies, and preferences | Missing metadata folder with screenshots for store submission |
35 files reviewed, 2 comments
…command screenshots;
|
GreptileBot comments fixed |
This comment was marked as duplicate.
This comment was marked as duplicate.
Sorry, something went wrong.
pernielsentikaer
left a comment
pernielsentikaer
left a comment
There was a problem hiding this comment.
Is the name Uranium or NFT Primitive Tools
| const { defineConfig } = require("eslint/config"); | ||
| const raycastConfig = require("@raycast/eslint-config"); | ||
|
|
||
| module.exports = defineConfig([ | ||
| ...raycastConfig, | ||
| { | ||
| rules: { | ||
| // Allow 'any' types with warning instead of error | ||
| "@typescript-eslint/no-explicit-any": "off", | ||
|
|
||
| // Allow unused vars that start with underscore (common pattern for TODO params) | ||
| "@typescript-eslint/no-unused-vars": [ | ||
| "warn", | ||
| { | ||
| argsIgnorePattern: "^_", | ||
| varsIgnorePattern: "^_", | ||
| destructuredArrayIgnorePattern: "^_" | ||
| } | ||
| ], | ||
|
|
||
| // Allow unused parameters that start with underscore | ||
| "no-unused-vars": "off", // Turn off base rule as it conflicts with TypeScript rule | ||
| }, | ||
| }, | ||
| ]); |
There was a problem hiding this comment.
Can we keep
const { defineConfig } = require("eslint/config");
const raycastConfig = require("@raycast/eslint-config");
module.exports = defineConfig([
...raycastConfig,
]);
“Uranium” is our project name, while the extension name is “NFT Primitive Tools” |
|
Fixed |
|
@pernielsentikaer Can are you merge this? |
|
Is there any way to merge this? |
|
Published to the Raycast Store: |
|
🎉 🎉 🎉 Such a great contribution deserves a reward, but unfortunately we couldn't find your Raycast account based on your GitHub username (@xkelxmc). |
3 participants
Description
Screencast
Checklist
npm run buildand tested this distribution build in Raycastassetsfolder are used by the extension itselfREADMEare placed outside of themetadatafolder