Integrate bitemporal SQL reporting service (Tech Sprint 2024)#237
Draft
refset wants to merge 96 commits intofinos:mainfrom
Draft
Integrate bitemporal SQL reporting service (Tech Sprint 2024)#237refset wants to merge 96 commits intofinos:mainfrom
refset wants to merge 96 commits intofinos:mainfrom
Conversation
added 30 commits
August 20, 2024 13:02
TODO: pass on the price to trade blotter and position and persist trades in XTDB
consider if all prices or only those asked for
use styles to highlite background for gain/loss
Fetch data on slider release
To prevent horizontal scrolling
✅ Deploy Preview for lucky-concha-f3599f ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This Draft PR presents a set of changes delivered as part of JUXT's involvement with the Tech Sprint. The changes may be reviewed, discussed and considered for upstream usage as desired.
The changes are documented in this README.
However, based on recent discussions with key community members, it sounds likely that the ultimate approach to integrating the bulk of these changes (if at all) will depend on there first being some 'knowledge graph' strategy implemented within this repo.
Please advise if there are obvious changes we could make to aid with reviewing/assessing/discussing, thanks.