Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Two package.json in project lack sufficient distinguishing documentation
See original GitHub issueThe project includes /package.json and /contracts/package.json and publishes @openzeppelin/contracts and openzeppelin-solidity respectively. I’m sure there is some good, well-thought-out reason for this.
The two files contribute the same description of Secure Smart Contract library for Solidity and look mostly the same inside.
To improve maintainability of these two files, some note should be added inside (e.g. "note":) each describing the difference between the two files or where responsibility of one ends and the other starts.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I did not mean identical in every way… The files cannot be identical. The contracts on npm are the same in both packages. There are differences that are not of substance.
Please don’t make any changes to the package.json files.
The two files are not currently identical
https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/package.json https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/package.json
Shall I update one to equal the other? Which one shall keep?