-
Notifications
You must be signed in to change notification settings - Fork 20
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
Added Interactive Brokers Tiered pricing #29
Open
sirchia
wants to merge
2
commits into
nicwortel:master
Choose a base branch
from
sirchia:add-interactive-brokers-tiered
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Misschien wel even vastleggen hoe je aan deze 0,0558% komt. Want dit is je eigen benadering zodat het in dit model past.
Als ik even snel kijk dan klopt dit best redelijk. Alleen voor de inleg rond de 2500-6500 zit je ietwat aan de lage kant. Maar goed, dat gaat even niet anders in deze setup.
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.
JSON staat officieel volgens mij geen commentaar toe in het formaat, of is de door jullie gebruikte parser daar wat flexibeler in? Hoe/waar stel je anders voor dit te documenteren?
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.
Die zou ik ff met @nicwortel checken, anders een losse readme.md ergens er bij?
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.
JSON ondersteunt inderdaad geen native comments, maar ik ben het met @gerbenvl eens dat het wenselijk is om hier wel wat uitleg bij te geven. Met name zodat in de toekomst makkelijk te herleiden is of de gebruikte tarieven nog up-to-date zijn of bijgewerkt moeten worden.
Wat wel kan is het toevoegen van extra properties aan de JSON, die niet uitgelezen worden door de code maar wel wat context kunnen geven.
Technisch gezien kan zo'n property elke willekeurige key/naam hebben die nog niet in gebruik is, maar om duidelijk te maken dat het om een comment gaat die geen effect heeft op de werking van de website zou het mijn voorkeur hebben dat zo'n property een naam als
_comment
of iets dergelijks heeft.Bijvoorbeeld: