-
Notifications
You must be signed in to change notification settings - Fork 771
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Monorepo: remove default exports #2018
Conversation
Codecov Report
Flags with carried forward coverage won't be shown. Click here to find out more. |
33db4c5
to
6e08e3b
Compare
9078f91
to
1b99dbb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just went through for a first round, some things to address, generally this looks really really great though, thanks for all the work here!! 😄 👍
Please be really careful on the branch update with the VM/EVM README files since I put a lot of work in these rewriting the text and coming up with an adopted structure. So please do not use the merge function or so, this will close to for sure not work. I guess best rather is here to just copy over the versions from master
and the manually re-apply the path adoptions, can't imagine that there is another chance to get this done right.
Also: I would like to merge this in early here, since changes are so vast, this will likely get conflicting with other work pretty quickly (I e.g. already postponed additional README work on the other libs today due to some fear of getting into the same situation as in VM/EVM again).
So, in case this isn't complete yet, it would be good if we can in doubt rather fix the current state and then merge here and do the work on top in favor of having these open for several more days. But for sure also totally depends on a) what's open and b) what are your free times to tackle. So this is rather just a general note and very much needs to be adopted to the situation.
packages/block/CHANGELOG.md
Outdated
// Provide your block data here or use default values | ||
}, | ||
{ common } | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, please do not change code examples from CHANGELOG files from the older (non-beta) library versions. The CHANGELOG examples are always "tied" to the respective versions, otherwise it would make not much sense.
Sorry, this might get a bit laborious, since this is actually present in all/most CHANGELOG files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I left the changes in the .md files in a separate commit so that they're easily removable, but I'm unsure why a lot of this sort of formatting was automatically done, I assumed it was project-configured formatting that only got triggered now that changes were made to these files? Anyhow will revert most of these, if we want to improve .md formatting we can always do it in another PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
| `blockchain:clique` | Clique operations like updating the vote and/or signer list | | ||
| Logger | Description | | ||
| ------------------- | ----------------------------------------------------------- | | ||
| `blockchain:clique` | Clique operations like updating the vote and/or signer list | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I am not such a fan of these corrections, since this also renders correctly with the short version, so this just leads to slightly more work, since one now always has to adopt the length when rewriting the description.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the plus side I see that this is somewhat more readable in the raw format.
Not sure, maybe there are also other opinions from the team and we can find a rather common ground? Also do not want to impose my personal preferences here (and some similar other locations).
packages/evm/CHANGELOG.md
Outdated
|
||
const common = new Common({ chain: Chain.Mainnet, hardfork: Hardfork.Merge }) | ||
const vm = new VM({ common }) | ||
vm._common.isActivatedEIP(4399) // true | ||
``` | ||
|
||
- [EIP-4399](https://eips.ethereum.org/EIPS/eip-4399) Support: Supplant DIFFICULTY opcode with PREVRANDAO, PR [#1565](https:// | ||
github.com/ethereumjs/ethereumjs-monorepo/pull/1565) | ||
github.com/ethereumjs/ethereumjs-monorepo/pull/1565) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, no, these kind of format corrections are not correct, this simply destroys the correct rendering and draws the URL apart, see the rendered version of this file.
Please make sure that you haven't updated anywhere else in a similar fashion.
packages/evm/CHANGELOG.md
Outdated
@@ -439,7 +439,7 @@ See PR [#1198](https://github.com/ethereumjs/ethereumjs-monorepo/pull/1198). | |||
|
|||
**Features** | |||
|
|||
- Added `receipt` to `RunTxResult`, moved the tx receipt generation logic from `VM.runBlock()` to `VM.runTx()` (`generateTxReceipt()` and receipt exports in `runBlock` are now marked as *deprecated*), PR [#1185](https://github.com/ethereumjs/ethereumjs-monorepo/pull/1185) | |||
- Added `receipt` to `RunTxResult`, moved the tx receipt generation logic from `VM.runBlock()` to `VM.runTx()` (`generateTxReceipt()` and receipt exports in `runBlock` are now marked as _deprecated_), PR [#1185](https://github.com/ethereumjs/ethereumjs-monorepo/pull/1185) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious, since these corrections are all over the place: isn't *deprecated*
(e.g.) correct markdown? 🤔
@@ -1,7 +1,7 @@ | |||
import { PrecompileInput } from './types' | |||
import { OOGResult, ExecResult } from '../evm' | |||
|
|||
export default function (opts: PrecompileInput): ExecResult { | |||
export function precompile04(opts: PrecompileInput): ExecResult { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, definitely a better name than my pc
suggestion. 🙂
1b99dbb
to
2c95530
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love it (to speak with Tim Beiko 😋), also thanks for addressing this so quickly then I can continue with the README updates today! ❤️
Also totally love the linting rule and the generality of this - thanks for suggesting - this is now just such a pure simplification and a general we-are-done-with-it thing - really with no substantial downsides - always great to have these structural simplifications in the whole monorepo where one has the feeling that things just get easier to handle.
Will merge.
This PR removes all instances of default exports within the monorepo. It also adds the
'import/no-default-export'
linting rule that will prevent the addition of new default exports.Resolves #2013