@prb/test - npm Package Compare versions
Comparing version 0.1.1 to 0.1.2
@@ -7,2 +7,8 @@ # Changelog | ||
| ## [0.1.2] - 2022-07-17 | ||
| ### Fixed | ||
| - Switch to global import to fix the overload type checker bug in Solidity v0.8.12 ([#5](https://github.com/paulrberg/prb-test/issues/5)) (@jordaniza, @paulrberg) | ||
| ## [0.1.1] - 2022-07-15 | ||
@@ -12,3 +18,3 @@ | ||
| - Add `pinst` as Node.js dev dependency to disable the `postinstall` life cycle script in production (@paulrberg). | ||
| - Add `pinst` as Node.js dev dependency to disable the `postinstall` life cycle script in production (@paulrberg) | ||
@@ -21,3 +27,4 @@ ## [0.1.0] - 2022-07-15 | ||
| [0.1.2]: https://github.com/paulrberg/prb-test/releases/tag/v0.1.2 | ||
| [0.1.1]: https://github.com/paulrberg/prb-test/releases/tag/v0.1.1 | ||
| [0.1.0]: https://github.com/paulrberg/prb-test/releases/tag/v0.1.0 |
| { | ||
| "name": "@prb/test", | ||
| "description": "Modern collection of testing assertions and logging utilities for Solidity", | ||
| "version": "0.1.1", | ||
| "version": "0.1.2", | ||
| "author": { | ||
@@ -6,0 +6,0 @@ "name": "Paul Razvan Berg", |
@@ -29,3 +29,3 @@ # PRBTest [![Github Actions][gha-badge]][gha] [![Foundry][foundry-badge]][foundry] [![Styled with Prettier][prettier-badge]][prettier] [![License: MIT][license-badge]][license] | ||
| ```sh | ||
| forge install --no-commit paulrberg/prb-test@0.1.1 | ||
| forge install --no-commit paulrberg/prb-test@0.1.2 | ||
| ``` | ||
@@ -37,3 +37,3 @@ | ||
| [submodule "lib/prb-test"] | ||
| branch = "0.1.1" | ||
| branch = "0.1.2" | ||
| path = "lib/prb-test" | ||
@@ -59,5 +59,5 @@ url = "https://github.com/paulrberg/prb-test" | ||
| Once installed, all you need to do is import the `PRBTest` contract and inherit from it in your test contract. `PRBTest` | ||
| comes with a pre-instantiated [cheatcodes](https://book.getfoundry.sh/cheatcodes/) environment accessible via the | ||
| `vm` property. It also has support for logs. | ||
| Once installed, all you need to do is import `PRBTest` and inherit from it in your test contract. `PRBTest` comes with a | ||
| pre-instantiated [cheatcodes](https://book.getfoundry.sh/cheatcodes/) environment accessible via the `vm` property. It | ||
| also has support for logs. | ||
@@ -128,5 +128,5 @@ ```solidity | ||
| Also, the DSTest testing assertions are not themselves tested. But the PRBTest testing assertions are tested, and in | ||
| Also, the DSTest testing assertions are not themselves tested. Whereas the PRBTest testing assertions are tested, and in | ||
| fact they are quite thoroughly tested. All other things being equal, this should give you more confidence that your | ||
| tests do what you intend them to do with PRBTest. | ||
| tests do what you intend them to do. | ||
@@ -136,7 +136,7 @@ ### 2. No Release Versioning | ||
| DSTest doesn't version its releases, which makes it difficult to future-proof consumer repos. It's quite easy to | ||
| to accidentally update your git submodules and thus break your test suites. For some users, this is a [real pain](https://github.com/dapphub/ds-test/issues/32). | ||
| to accidentally update your git submodules and thus break your test suites. For [some users](https://github.com/dapphub/ds-test/issues/32), this is a real pain. | ||
| PRBTest is versioned via tags and branches and all changes are tracked in a [CHANGELOG](./CHANGELOG.md) file. I maintain redundant branches for each release because git submodules [don't support tags](https://stackoverflow.com/q/1777854/3873510). | ||
| I strive to follow the [semver](https://semver.org/) versioning scheme, though I won't do this before the v1.0 release, and it might not always be feasible. | ||
| I will strive to follow the [semver](https://semver.org/) versioning scheme, though I won't do this before the v1.0 release, and it might not always be feasible. | ||
@@ -153,3 +153,3 @@ ### 3. Path Dependence | ||
| This issue has led to a "balkanization" of DSTest forks and extensions. See, for instance, Solmate's [DSTestPlus][ds-test-plus] and Forge Std's | ||
| [Test][forge-std-test] contracts. Also, as a case in point, see the discussions in this [PR](https://github.com/foundry-rs/forge-std/pull/38), in which the PR | ||
| [Test][forge-std-test]. Also see the discussions in this [PR](https://github.com/foundry-rs/forge-std/pull/38), in which the PR | ||
| author ended up making the PR against `forge-std` rather than `ds-test` because he feared that his PR won't be merged in | ||
@@ -160,3 +160,3 @@ the latter. | ||
| It's my firm conviction that Foundry is the future of Ethereum smart contract development. Solidity code is best tested in Solidity itself. | ||
| It i my firm conviction that Foundry is the future of Ethereum smart contract development. Solidity code is best tested in Solidity itself. | ||
@@ -163,0 +163,0 @@ But, due to various historical reasons, the Ethereum ecosystem has for a long time relied upon JavaScript for testing smart contracts. |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by0.25%
69839