Open
Conversation
feat(build): introduce Makefile for streamlined build, dev, and clean operations docs(readme): add development instructions using Docker and locally feat(ci): create docker-compose.yml to facilitate development environment setup
chore(deps): add fetch-pr-statuses script to package.json
feat(navigation): add route for individual devnet spec sheets
feat(DevnetSpecPage): add DevnetSpecPage component to display EIP specs and implementation status
This adds a new page component dedicated to displaying the specification details for a given development network ('Devnet').
The component fetches spec data using `useDevnetSpec`, sets appropriate meta tags via `useMetaTags`, and renders:
1. General metadata (launch date, spec versions, upgrade name).
2. A matrix showing implementation status for Execution Layer (EL) and Consensus Layer (CL) clients based on their version or support status.
3. A tracker for related Pull Requests (PRs) merged/open for each EIP relevant to this devnet.
This provides users with a centralized view of what EIPs are targeted and which client implementations have achieved the required status. Utility components like `ChangeStatusBadge`, `ImplStatusCell`, and `PRStatusBadge` are introduced to format status indicators consistently.
feat(ui): display EIP status and implementation matrices
Introduce rendering logic for EIP status and implementation tracking for both Execution Layer (EL) and Consensus Layer (CL) clients.
This provides users with a clear, responsive view (desktop table and mobile cards) detailing:
1. Associated PRs for each EIP.
2. Client implementation status against each EIP, facilitating better tracking of Ethereum Upgrade progress.
refactor(ui): group and style tracked PRs in DevnetSpecPage for clarity
Organize the display of tracked Pull Requests (PRs) by grouping them according to their repository using predefined category order.
This change improves readability and scannability by:
1. Grouping PRs associated with 'ethereum/EIPs', 'execution-specs', 'consensus-specs', and 'execution-apis' together, with clear section headers.
2. Sorting the groups based on this predefined order.
3. Implementing consistent table layout for desktop views and card layout for mobile views, including status badges.
feat(devnet-specs): add bal-devnet-2 genesis specification file
Add the specification file for the fictional 'bal-devnet-2'. This file details the EIPs included, consensus/execution spec versions, and implementation statuses for a hypothetical devnet upgrade named "glamsterdam".
chore(deps): update EIP metadata to include recent PRs
This updates the cached data about related EIPs by incorporating recent pull requests from various Ethereum repositories (`execution-specs` and `execution-apis`). This is necessary to keep the tracking of EIP statuses and specifications up-to-date.
feat(hooks, types): introduce useDevnetSpec hook and DevnetSpec types
Introduce a new React hook `useDevnetSpec` to fetch and manage the data for a specific devnet specification located in a local JSON file.
This required creating new TypeScript types (`DevnetSpec`, `DevnetSpecEip`, etc.) in `src/types/devnet-spec.ts` to model the structure of the devnet specification data. The main types file is updated to re-export these new types.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
feat(ci): add script and route to fetch PR statuses for devnet specs
chore(deps): add fetch-pr-statuses script to package.json
feat(navigation): add route for individual devnet spec sheets
feat(DevnetSpecPage): add DevnetSpecPage component to display EIP specs and implementation status
This adds a new page component dedicated to displaying the specification details for a given development network ('Devnet').
The component fetches spec data using
useDevnetSpec, sets appropriate meta tags viauseMetaTags, and renders:This provides users with a centralized view of what EIPs are targeted and which client implementations have achieved the required status. Utility components like
ChangeStatusBadge,ImplStatusCell, andPRStatusBadgeare introduced to format status indicators consistently.feat(ui): display EIP status and implementation matrices
Introduce rendering logic for EIP status and implementation tracking for both Execution Layer (EL) and Consensus Layer (CL) clients.
This provides users with a clear, responsive view (desktop table and mobile cards) detailing:
refactor(ui): group and style tracked PRs in DevnetSpecPage for clarity
Organize the display of tracked Pull Requests (PRs) by grouping them according to their repository using predefined category order.
This change improves readability and scannability by:
feat(devnet-specs): add bal-devnet-2 genesis specification file
Add the specification file for the fictional 'bal-devnet-2'. This file details the EIPs included, consensus/execution spec versions, and implementation statuses for a hypothetical devnet upgrade named "glamsterdam".
chore(deps): update EIP metadata to include recent PRs
This updates the cached data about related EIPs by incorporating recent pull requests from various Ethereum repositories (
execution-specsandexecution-apis). This is necessary to keep the tracking of EIP statuses and specifications up-to-date.feat(hooks, types): introduce useDevnetSpec hook and DevnetSpec types
Introduce a new React hook
useDevnetSpecto fetch and manage the data for a specific devnet specification located in a local JSON file.This required creating new TypeScript types (
DevnetSpec,DevnetSpecEip, etc.) insrc/types/devnet-spec.tsto model the structure of the devnet specification data. The main types file is updated to re-export these new types.