docs(readme): correct artifact copy path and flattened destination filename #1071
Conversation
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
1 participant
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.
This change updates the deployment instructions to copy the exact ABI file produced by Hardhat from apps/contracts/artifacts/contracts/Feedback.sol/Feedback.json to a flattened path at apps/web-app/contract-artifacts/Feedback.json, which matches how the web app imports the artifact (e.g., src/app/api/feedback/route.ts and src/app/group/page.tsx). The previous guidance suggested copying the whole artifacts/contracts folder, which would result in a nested Feedback.sol/Feedback.json path that breaks imports. Aligning the README with the actual import shape avoids runtime module resolution errors and ensures a smooth setup.