Skip to content
This repository was archived by the owner on Jun 24, 2022. It is now read-only.

Price estimation Fee API #36

Merged
merged 26 commits into from
Dec 18, 2020
Merged

Conversation

W3stside
Copy link
Contributor

@W3stside W3stside commented Dec 4, 2020

Part of #32

Merges into #33

Summary

  • Creates mock api endpoint fn, getFee for grabbing FeeInformation object, passing sellToken address as arg

@W3stside W3stside changed the base branch from develop to price-estimation-intercept December 4, 2020 17:29
@W3stside W3stside marked this pull request as draft December 4, 2020 17:29
@ghost
Copy link

ghost commented Dec 4, 2020

Travis automatic deployment:

  • 🎩 Dapp: Testing web app

@W3stside W3stside force-pushed the price-estimation-fee-api branch from 78eb812 to f90206f Compare December 4, 2020 17:50
@W3stside W3stside mentioned this pull request Dec 9, 2020
@W3stside W3stside marked this pull request as ready for review December 9, 2020 11:10
@W3stside W3stside requested review from Velenir and anxolin December 9, 2020 11:10
@W3stside W3stside changed the base branch from price-estimation-intercept to develop December 9, 2020 11:10
@W3stside W3stside changed the base branch from develop to price-estimation-intercept December 9, 2020 11:11
@W3stside W3stside marked this pull request as draft December 9, 2020 11:11
@W3stside W3stside changed the base branch from price-estimation-intercept to develop December 9, 2020 11:16
@W3stside W3stside force-pushed the price-estimation-fee-api branch from 23dad10 to 57bf93f Compare December 9, 2020 11:16
@W3stside W3stside force-pushed the price-estimation-fee-api branch from 57bf93f to c8519d3 Compare December 9, 2020 11:36
@W3stside W3stside marked this pull request as ready for review December 9, 2020 11:41
@W3stside W3stside force-pushed the price-estimation-fee-api branch from db2ca04 to 8a93d5a Compare December 9, 2020 11:45
}

const initialState: FeeInformationState = {
feesMap: {}
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we also differentiate by chainId or do we count on token addresses not overlapping over diff networks?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

hmm true, likely will. @anxolin thoughts

Copy link
Contributor

Choose a reason for hiding this comment

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

token addresses do overlap in different networks

@W3stside W3stside force-pushed the price-estimation-fee-api branch from 992d21a to f47937b Compare December 17, 2020 09:59
@W3stside W3stside changed the base branch from develop to release/v0.2.0-DEMO December 18, 2020 08:59
@W3stside W3stside force-pushed the price-estimation-fee-api branch from f47937b to 0e425a5 Compare December 18, 2020 09:03
@W3stside W3stside merged commit fbac962 into release/v0.2.0-DEMO Dec 18, 2020
@W3stside W3stside deleted the price-estimation-fee-api branch December 18, 2020 13:26
W3stside pushed a commit that referenced this pull request Jun 28, 2021
add typechain generation for core/periphery contracts
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants