🎉 initial version of constants for kodadot

[vikiival]

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.

PR type

• Fix
• Feature
• Refactoring
• Chore

What's new?

• PR refs Rethink how we are adding new chains #102

[vikiival]

Please if I forgot something, pls let me know.
Or if you advise any other data type or so.

[roiLeo]

gh workflow won't work inside static should be at root level

Not sure if it's a good idea to centralized config in a fixed package version.

What would be the steps if we need to make a quick update on relay chain because one of them is dead? (same stuff for squid version upgrade/downgrade)

[vikiival]

gh workflow won't work inside static should be at root level

fixed in #111

What would be the steps if we need to make a quick update on relay chain because one of them is dead?

Not sure what you mean?

[roiLeo]

Not sure what you mean?

Let's say new squid rmrk2 (rc1) out, to make progress on developments we will have to wait for a new package release.
And what if now the squid endpoint broke then new package release to fallback previous endpoint, update the package version on marketplace and then update it again a few days later.

or I extrapolate a bit

[vikiival]

Let's say new squid rmrk2 (rc1) out, to make progress on developments we will have to wait for a new package release.
And what if now the squid endpoint broke then new package release to fallback previous endpoint, update the package version on marketplace and then update it again a few days later.

The intention of the package is to make some constants static something that would not change. For development purposes I would definitely extend package on frontend.

Second things is that we have a ton of obsolete code on the frontend.

[Jarsen136]

LGTM

[preschian]

Not sure what you mean?

we will have to wait for a new package release

I only know two methods to address this

1. use pnpm workspaces. this is what we use with @kodadot1/brick. it means, we need to merge the packages repo inside the nft-gallery. https://pnpm.io/workspaces#referencing-workspace-packages-through-aliases. we can use it directly without waiting to release. and we can publish the packages
2. because npm does not support installing GitHub URLs with subfolders. we need to turn folders into branches first. https://stackoverflow.com/a/69365523. after that, we can install the package npm install https://github.com/username/repo#branch. I think we need to set up gh-actions for this. to update the branch every time there is a commit into the main branch. (actually, this is similar with wait for the release)

[vikiival]

@preschian @roiLeo if it makes more sense for you i can move it under the nft-gallery so it will be awailable directly in the workspace.

I just need these constants across the other packages (uniquery, vuex-options)

WDYT?

[preschian]

move it under the nft-gallery

hhmm, maybe try this first? and let's see what happens next