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: Sonic Ecology Entry #2619

Open
wants to merge 13 commits into
base: develop
Choose a base branch
from

Conversation

christianholman
Copy link

No description provided.

@christianholman
Copy link
Author

Couple of things to clarify:

  • Am I adding the chain metadata correctly?
  • Are there any places I'm re-doing things that are already util functions, such as fetching and caching?

@christianholman christianholman marked this pull request as ready for review November 12, 2024 12:25
@christianholman christianholman marked this pull request as draft November 12, 2024 12:27
.envrc Outdated
@@ -0,0 +1 @@
use flake
Copy link
Member

Choose a reason for hiding this comment

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

Can remove all flake related code? I don't see any real use for it.

@@ -0,0 +1,3 @@
{
"recommendations": ["dbaeumer.vscode-eslint"]
}
Copy link
Member

Choose a reason for hiding this comment

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

please remove auto-generated code from your vscode

Copy link
Author

Choose a reason for hiding this comment

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

Neither the flake file nor the ide extension metadata are autogenerated, they're very helpful to get productive without running into a bunch of linting errors etc when the editors are not aware of what sort of codebase is being dealt with, as well as for being able to switch between eslint/non-eslint repos. The flake stuff is for running a shell with node/yarn available, very useful for running an isolated dev environment inside the repo.

Just for some context on why I used them here, nothing overrides the user's editor setup an are just hints if they have no formatting etc to align with your eslint rules!

Will remove them for now and can merge them back again if you see the value :)

@christianholman christianholman marked this pull request as ready for review November 12, 2024 22:04
@christianholman christianholman marked this pull request as draft November 12, 2024 22:04
const [hasCopied, setHasCopied] = useState(false);
const { t } = useTranslation();

const copyToClipboard = async (text: string, options: CopyOptions = {}) => {
Copy link
Member

Choose a reason for hiding this comment

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

@@ -79,3 +79,14 @@ export const safeJSONParse = (str: string) => {
return null;
}
};

export const formatAddress = (address?: string, n = 4) => {
Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Author

Choose a reason for hiding this comment

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

for sure, thanks for pointers

@christianholman christianholman marked this pull request as ready for review November 14, 2024 10:52
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