-
Notifications
You must be signed in to change notification settings - Fork 25
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
Refactoring sqPath #2986
Merged
Merged
Refactoring sqPath #2986
Changes from 19 commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
4c3eaee
Refactoring sqPath
OAGr 9957e1c
Merge branch 'main' into sqPath-refactor
OAGr 28ae223
Small fixes for tests
OAGr 44b4db9
Testing SqValuePath
OAGr 8361d0c
Minor fix
OAGr 29c5ae3
useGetSubValueByPath cleanup
OAGr 7963a45
Minor cleanup
OAGr a8f8af6
Test cleanup
OAGr 84e1778
Further cleanup
OAGr c5c5c31
Merged with main
OAGr 5a513a0
Minor cleanup
OAGr e3bbc99
Changed SqPathItem to use 'dictKey' and 'arrayIndex'
OAGr 5da319e
Fixed tests
OAGr 643acef
pathAsString -> path.uid() and pathToDisplayString()
OAGr b4643c1
SqPathItem -> SqValuePathEdge
OAGr 3674260
Renamed PathEdge dictKey and arrayIndex
OAGr d0b0d70
Changed SqValuePath node to edge
OAGr 958bc82
Responded to CR
OAGr 4e368c2
Moved getSubvalueByPath to SqValue
OAGr b15fc1c
Refactored allPrefixPaths
OAGr f8fc608
Merge branch 'main' into sqPath-refactor
OAGr 76a9f2a
fix hub types
berekuk 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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Could be
path.toDisplayString()
(or
path.toString()
, see my other comment)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.
The annoying thing here is that in
utils
, we use different names for the root elements than insquiggle-lang
. I could do a regex to replace, but that seemed hacky.Maybe we could rename them in
squiggle-lang
to matchSquiggle-viewer
? "Bindings" -> "Variables", capitalize all of them?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.
Hmm. Yeah, I missed that this depends on
topLevelName
.The problem with renaming is that roots also match keys in
SqOutput
dicts, and it's nice even if we don't rely on it anywhere.In
export type ValuePathRoot = "result" | "bindings" | "imports" | "exports"
, I thought about suggestingexport type ValuePathRoot = keyof SqOutput
, but they might diverge at some point (output could include other, non-value things), so I'm not sure if that's a good idea.Using public names in
SqOutput
is too much (and problematic re: versioned-components), so... I dunno. Maybe just leave it here for now.