Skip to content

Conversation

edemaine
Copy link
Collaborator

@edemaine edemaine commented Jun 9, 2022

This PR deletes the data from src/pages/Resources/*.data.ts, so should be merged only after moving the latest Ecosystem data to solidex.

@davedbase
Copy link
Member

@edemaine I'm ready to tackle this tomorrow btw. Everything should be prepared in ecosystem to build and publish to npm then I can update it here, compile and deploy. Is this correct or am I missing some effort?

@edemaine
Copy link
Collaborator Author

Here's a plan:

  1. Could you start with reviewing Port to JSON, rework TypeScript types solidex#2? I think it's ready, except possibly deciding on a better file naming scheme.
  2. Then we should check that the API can consume the new solidex repo properly. Does it use NPM or the repo or ...? I wrote code for NPM building, but if it relied on JSON in the GitHub repo it might not work.
  3. Then I can update this solid-site PR to consume the new solidex data format correctly. (In particular dates will need to be parsed from strings instead of numbers; I think that's all.)
  4. At this point we can accept ecosystem PRs on solidex instead of solid-site. An improvement? 😅
  5. Then I need to make the actual form for ecosystem submissions that calls the API / we need to update/test the API PR generation mechanism (which at least will need to be updated to the new solidex repo format).

@davedbase davedbase closed this Jun 7, 2024
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