Closed OAGr closed 9 months ago
Latest commit: e1ee728c2b4d005f6225fad58a8363cf9da9e2d5
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Updated (UTC) |
---|---|---|---|
quri-hub | ✅ Ready (Inspect) | Visit Preview | Jan 31, 2024 8:44pm |
squiggle-components | ✅ Ready (Inspect) | Visit Preview | Jan 31, 2024 8:44pm |
squiggle-website | ✅ Ready (Inspect) | Visit Preview | Jan 31, 2024 8:44pm |
After this goes in, we should change exportData
to also be a type.
After this goes in, we should change
exportData
to also be a type.
Later we might have to change it back to being a VDict
, or a custom struct Value
. I understand that using a type gives us type safety, though. Depends mostly on how soon we get custom structs, and how compile-time-safe they're going to be (will stdlib custom structs be shaped with TypeScript generics to map to TS object shapes? seems doable but difficult to predict).
One key consideration is if we can auto-add @location on decorators. If we can, then I think this should be named
@location
, as I don't expect it to be frequently used. If we can't, then I think we should name it@loc
.There's a significant issue with this PR, as I had to make a new
ValueTagsWrapper
class to handle some functions onValueTags
, due to an issue of circular dependencies. Curious if you have preffered ways of doing this. I also considered havingBaseValue
rely on an abstract class version ofValueTags
, but that seemed like too much.Tests are failing because the new
toString
format is different. If this PR is approved, I'll fix these.