Closed wackywendell closed 4 weeks ago
Sorry for the force-push - I usually try not to do that, but as no one had reviewed yet and the CI was failing on commit messages, I figured I'd fix those.
Next time I'll plan to make a Draft PR first, get it passing CI, then mark it for review.
@mbrobbel - thanks! Is this ready to merge, then? If so, can you do that - I don't have permissions?
@mbrobbel - thanks! Is this ready to merge, then? If so, can you do that - I don't have permissions?
Let's get #282 in first, then rebase/merge here to fix CI.
@mbrobbel - thanks for approving and merging #282!
I can either rebase this on main (post #282), then force-push, which will be "cleaner" git history with the downside of making reviews harder to follow, or I can merge in main. Any preferences?
@mbrobbel - thanks for approving and merging #282!
I can either rebase this on main (post #282), then force-push, which will be "cleaner" git history with the downside of making reviews harder to follow, or I can merge in main. Any preferences?
It doesn't really matter because we squash merge in the substrait-io
org. This will be one commit on main
.
OK, main merged in, let's see how CI goes... ⏳
And CI passed! 🎉
Also refactors the parse / validation layer a bit to separate them a bit more.
Addresses #280.
I'm still fairly new to this code / repo, so I took a bit of time to see if I could address #280 in the "naive" way. Naive solutions are often as good as any... but sometimes, they are naive, so let me know if there's something I'm missing or if this is something we should avoid exposing!