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.
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
feat(data-exploration): data exploration backend API with types #13933
feat(data-exploration): data exploration backend API with types #13933
Changes from 17 commits
a896737
1b55747
2c68681
4b5a595
3e3b1ec
3bf4a30
1e91573
5007caf
df9fd12
dd72cbe
12ec5ef
5546ca4
dec00a0
1863738
350ca11
334b3d7
d567a7c
f941eff
7c40322
6e08e9e
d02e4b7
8a223b2
62f3d46
efe5135
9701325
457bf4d
cccf24d
b085362
360f211
a77ab10
d8256b1
6aa4064
8aadcdd
2b86581
4f4a840
2760a0c
3cce8b5
e42bc9f
511f040
8756d17
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
If
schema.json
andschema.py
are only generated from this file, do we need to commit them? I can see this being a bit easier, but I'm a bit worried about them getting of out of sync as it's possible to commit changes to the wrong file. Plus they're really big. Could be compiled in package.json'sprepare
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.
Says the guy who just committed gigabytes of PNGs to the repo :D.
Just like snapshots, I'm afraid if we don't commit them to git, we won't see any unexpected changes in the schema. Since this is a very important schema that'll be used to generate public facing docs, tooling for users, etc, I'd prefer to not take any chances.
It also makes development easier, if the files are already there. Unrelated, I've also been playing around with a Kea typegen inline types mode that would also commit the types into the repo... for clean, fast and reproducible builds.
Also, I still want to add a github action that throws a wrench when the schema is out of sync.
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.
Having the kea types ship with git would help a lot for reviews etc. where switching branches takes a bit of time at the moment, so +1 for a solution there.
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.
Isn't
schema.ts
the snapshot in this case? The derived.json
and.py
versions ones are just distractions in a code review.But fair enough, should be okay IF we have a wrench-throwing action.