Skip to content
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

handle all arc.js datetime types #2002

Merged
merged 5 commits into from
Jul 26, 2020
Merged

Conversation

dkent600
Copy link
Contributor

@dkent600 dkent600 commented Jul 24, 2020

Resolves: #1984

  • Adds safeMoment.
  • a couple other tweaks to attempt to ensure we're safe from any changes to arc.js wrt datetime typing
    • where Competition computes its status with respect to its workflow
    • where the vote buttons compute whether the proposal was created before the account had rep in the DAO

@dkent600 dkent600 requested review from orenyodfat and roienatan July 24, 2020 13:28
@dkent600 dkent600 self-assigned this Jul 25, 2020
@dkent600 dkent600 added the 2.0 label Jul 25, 2020
Copy link
Contributor

@roienatan roienatan left a comment

Choose a reason for hiding this comment

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

So if we solve this issue from arc.js this will not be necessary?

@dkent600
Copy link
Contributor Author

So if we solve this issue from arc.js this will not be necessary?

I'm not sure at the moment, would need to research it a bit. May depend on which data type is chosen. May not hurt to keep the change, just to be robust.

This line in particular should be checked:

image

@@ -301,7 +301,7 @@ export async function getNetworkId(web3Provider?: Web3Provider): Promise<string>
return network.chainId.toString();
} else {
const promise = new Promise<string>((resolve, reject) => {
web3Provider.send("net_version", (error, response) => {
web3Provider.send("net_version", (error: any, response: any) => {
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it related?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it is just the usual typescript lint warning improvements, an ongoing improvement...does not affect execution of the code.

Copy link
Contributor

Choose a reason for hiding this comment

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

ok, yes I assume also the boolean in proposalHelpers.ts

@dkent600 dkent600 merged commit 4f928d1 into dev-2 Jul 26, 2020
@dkent600 dkent600 deleted the fixCompetitionProposalCountdown branch July 26, 2020 10:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants