• Getting started
• Features
• Use cases
• Contributions
• License

Requires managing compiler

This seems to be because the state of FundContainer sets and keeps the render modal properties as true even when they're closed, so when the component re-renders they're both open. The solution may be to use redux, or to manage the state of the modals only FundContainer.

This is because it's converting from a date object to a timestamp before submitting the form. Instead, we'll check to see if it is the proper type before converting.

Also test to ensure that this doesn't happen with network changing as well.

May be worth holding back on doing this until we're ready to go live.

This appears on the invalid fund page.

Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
    in WithdrawForm (at FundContainer.js:40)
    in div (at FundContainer.js:37)

Although the UX of having a list of tokens to choose from is great, there are some little known tokens that users may also want to make use of.

Instead of grabbing the value of the amount of tokens in usd, we're just grabbing the value of one token in usd.

Will move function calls into sub-components after testing.

There are likely some optimizations that can be made relating to storage variables.

It looks like there is a better way to perform contract transactions using Drizzle. Take the time to read through this document to get a better understanding, and implement if desired.

https://www.trufflesuite.com/docs/drizzle/getting-started/contract-interaction

• Beneficiary address
  • Factory submit button should be disabled if address is invalid.
  • Should display, 'Invalid address'.
• Token contract address
  • Only applicable when custom token addresses are accepted.
• Updated owner/beneficiary address
  • Only applicable when feature is enabled.

We can probably do something similar to uniswap here:
https://github.com/Uniswap/uniswap-frontend/blob/beta/src/components/TokenLogo/index.js

At the moment, it is very hard to maintain the two components independently. Since they are effectively the same component, they should be consolidated.

Otherwise we'll probably leave some dust.

Something is causing an infinitely looping render again, which must be addressed.

• Fix validate dom nesting error
• Optimize page speed
  • This may not be possible without implementing the graph
• Consider styling changes

We always need to have an open path between pages, and since there's no navigation, they should all link to each other.

Probably just the logo spinning or something like that should suffice.

We want a similar UX to uniswap, allowing users to select/search for a coin from a dropdown menu.

Something similar to uniswap.

utils.js:271 Uncaught (in promise) Error: Given input "NaN" is not a number.

https://medium.com/trustless-fund/introducing-trustless-fund-67111a0869a6

https://app.gitbook.com/@kaden-zipfel/spaces

Might be worth displaying them somewhere other than it the wallet display. Let's begin with some designs on this.

e.g., this.props.drizzle.web3.utils...

It should go to mainnet etherscan in production but ropsten etherscan in development. In addition, it should be removed all together on local network.

It's trying to fetch the network id, and can't do it properly since it's not receiving the drizzleState.

Since different tokens have different numbers of decimals, we'll have to find the amount of decimals to convert to whole numbers as opposed to using from/toWei.

It's unlikely users want to immediately make another function, so after submission, we'll remove the form and add a 'Go to Fund' button and a 'Create Fund' button in case they want to create another fund.

Not sure if an issue with us or Metamask.

react_devtools_backend.js:6 MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 data listeners added. Use emitter.setMaxListeners() to increase limit

Instead, it should render necessary display components, but simply also display an error saying to change networks.

At the moment we pull in an example TrustFund contract object, but we want to grab the address from TrustFundFactory via the ID.

We may want to completely change the way we bring in the TrustFund contract anyway. For example, we don't need access to the contract object on the index page anyways, so we could perhaps only instantiate it on the Fund page and only after grabbing the address from the factory contract.

e.g. 'Max: 11.023'

Instead of the generic blue outline that you get when elements are focused, lets make it the brand color.

• Order token list.
  • It's ordered, but gets mixed up on search.
• Functional search input.
• Clicking away should close the dropdown.
• Button click should focus input.
• Button should have a down carat.
• Fix stock ERC20 token logo not working in button.
• Fix logos getting mixed up.
  • Easiest way to do this might be to add the logos to the token list object directly.
  • Note this only happens on search, so probably because they are staying in the same order.

This is a tough area, with lots of things to consider.

• How do we allow input of time-data?
  • Let's use this: https://reactdatepicker.com/
• How do we properly convert time data to Unix time?
• Let's set it to a user's local time.

Should be similar to the landing page.

Values that are reused throughout, such as border-radius should be represented with variables in case we decide to change them. Same goes for $color-brand: $color-gold instead of $color-gold directly.

https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html

e.g., Separate buttons into their own component so they can be reused.