Skip to content

Removed outdated section of primary package.json and add jsdoc comments#2303

Closed
amoweolubusayo wants to merge 12 commits intoethereum-optimism:developfrom
amoweolubusayo:develop
Closed

Removed outdated section of primary package.json and add jsdoc comments#2303
amoweolubusayo wants to merge 12 commits intoethereum-optimism:developfrom
amoweolubusayo:develop

Conversation

@amoweolubusayo
Copy link

Description
A clear and concise description of the features you're adding in this pull request.

Additional context
Add any other context about the problem you're solving.

Metadata

  • Fixes #[Link to Issue]

@changeset-bot
Copy link

changeset-bot bot commented Mar 9, 2022

🦋 Changeset detected

Latest commit: 19e1709

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages
Name Type
@eth-optimism/contracts Patch
@eth-optimism/data-transport-layer Patch
@eth-optimism/sdk Patch
@eth-optimism/message-relayer Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Add jsdoc comments to functions in contract package
@amoweolubusayo amoweolubusayo changed the title Removed outdated section of primary package.json Removed outdated section of primary package.json and add jsdoc comments Mar 9, 2022
}

export const getContractFactory = (
//returns the interface,bytecode and signer of a given contract by name.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are non standard jsdoc comments, usually they go above the function definition with a particular format

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep like @tynes said, here's an example of a standard jsdoc comment:

/**
* Applies the L1 => L2 aliasing scheme to an address.
*
* @param address Address to apply the scheme to.
* @returns Address with the scheme applied.
*/

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you so much! My bad. I would correct my PR.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New comments look great! Thank you :-)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got the new comments..would work on those! Thanks!

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. changeset added and rebase done.

Add jsdoc comments to contract-defs.ts
Copy link
Contributor

@smartcontracts smartcontracts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good, great job! Two quick things to resolve:

  1. Let's add a changeset for the contracts package so that your new jsdoc comments are published as part of the @eth-optimism/contracts package. You can see instructions for how to do this here.
  2. Let's also combine all of these changes into one commit that uses the conventional commit format. You can do this by running the command git rebase --interactive and following the instructions that appear there.


export const getContractDefinition = (name: string): any => {
/**
* Gets the contract's artifact
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a nit, but I think this should have a period after it for consistency.

This is what was done in the example given in @smartcontracts review:

/**
* Applies the L1 => L2 aliasing scheme to an address.
*
* @param address Address to apply the scheme to.
* @returns Address with the scheme applied.
*/

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it!

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for pointing that out.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are merge conflicts.. Am I to resolve that?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes please.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To do that, I would:

  1. fix the conflicts in package.json
  2. rerun yarn, which will overwrite the yarn.lock file with the correct contents.

Also don't forget to combine the commits per the comment above. :)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I have made the updates

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checks are failing. What can I do?

@maurelian
Copy link
Contributor

@amoweolubusayo sorry but it looks like you'll have to pull from master again, and then please also combine all of these changes into one commit that uses the conventional commit format. You can do this by running the command git rebase --interactive and following the instructions that appear there.

@github-actions github-actions bot added M-ci Meta: ci related work M-dtl A-pkg-sdk Area: packages/sdk labels Mar 18, 2022
@mergify
Copy link
Contributor

mergify bot commented Mar 31, 2022

Hey @amoweolubusayo! This PR has merge conflicts. Please fix them before continuing review.

@mergify mergify bot requested review from tuxcanfly and removed request for elenadimitrova April 4, 2022 18:45
@mergify mergify bot added the conflict label Apr 4, 2022
@github-actions
Copy link
Contributor

This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Apr 19, 2022
@github-actions github-actions bot closed this Apr 25, 2022
theochap added a commit that referenced this pull request Dec 10, 2025
… actors (#2303)

## Description

This PR does some structural services to the `RollupNodeService` trait,
in particular:
- It ensures we're only passing static configurations/builders to the
`NodeActor`s and offsets the building process to the `NodeActor` itself.
- Each actor now has an associated builder. This unifies the terminology
between `*Builder`s and `*Launcher`s which seemed to refer to the same
concept.
- This allows to simplify the `RollupNodeService` trait by having:
- less constraints on the configurations accepted by the `NodeActors`.
- having simpler associated methods which are basically just getters
over some fields of the `RollupNode`. No need for async associated
methods anymore or error handling.
- The only `.await` we're using is to spin up the actors once they're
initiated.
theochap added a commit that referenced this pull request Dec 10, 2025
## Description

This PR refactors the RPC actor in light of #2303 to unify its
interactions with the other actors. Simplifies a little bit the way we
handle RPC arguments by removing the `RpcBuilder` and move the
`RpcModule` handling inside the `RpcActor`
theochap added a commit that referenced this pull request Jan 14, 2026
## Description

This PR refactors the RPC actor in light of #2303 to unify its
interactions with the other actors. Simplifies a little bit the way we
handle RPC arguments by removing the `RpcBuilder` and move the
`RpcModule` handling inside the `RpcActor`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-pkg-sdk Area: packages/sdk M-ci Meta: ci related work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants