allow tables to have annotations#9613
allow tables to have annotations#9613sholderbach merged 6 commits intonushell:mainfrom 1Kinoti:table
Conversation
|
This is pretty cool ls | describe
table<name: string, type: string, size: filesize, modified: date> (stream)we still need to get our story straight in the codebase whether it's a |
i think |
amtoine
left a comment
There was a problem hiding this comment.
i'm not understanding all of the parsing changes, but it looks ok to me and the rest is great: the new vec![] in Table and the tests 👌
i'll approve this and let parser-experts have a look to the parser changes 😌
thanks @1Kinoti, as always great job 💪
@1Kinoti This is what I'm saying. We're inconsistent in our usage of date/datetime. Some places it's date. Other places it's datetime. I'm just saying we need to be consistent with whatever we use. Having said that, sorry for bringing up this discussion here since it has nothing to do with your PR. |
sholderbach
left a comment
There was a problem hiding this comment.
From my cursory reading of the parser nothing stands out to me, the implementation of SyntaxShape/Type looks good, and its great how you cover the happy and necessary unhappy paths.
As no existing tests had to change, I think we should move ahead and getting it into play testing!
|
oops, looks like there's a conflict now. :( |
|
agree with @sholderbach 👌 @1Kinoti, the conflict has been very likely introduced by #9404: the |
|
@amtoine since the review is done, i just rebased. hope this is okay :) |
mm, personally i dunno 🤔 from a reviewer's point of view, it broke the review as all the hashes changed, there is no merge commit and GitHub does not show the merge changes, rather everything that happened on the again, these are MY two cents, but i think rebasing once a review has started will allways break the review process at some point in the PR branch 😕 |
|
since the review has already been done, i think it's mostly okay, right? |
|
I am fine with it! |
Description
follow up to #8529 and #8914
this works very similarly to record annotations, only difference being that
more info on the syntax can be found here
User-Facing Changes
[BREAKING CHANGE]
this change adds a field to
SyntaxShape::Tableso any plugins that used it will have to update and include the field. though if you are unsure of the type the table expects,SyntaxShape::Table(vec![])will suffice