-
Notifications
You must be signed in to change notification settings - Fork 121
Add warning for when required bundle fields are not set #3044
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
Merged
Merged
Changes from all commits
Commits
Show all changes
34 commits
Select commit
Hold shift + click to select a range
b7e0bed
Generate required fields for DABs
shreyas-goenka 4c327c5
some cleanup
shreyas-goenka f612f5a
some cleanup
shreyas-goenka 9199d25
add generate
shreyas-goenka de8477e
fix and generate
shreyas-goenka 849787f
Merge remote-tracking branch 'origin' into generate-required-v3
shreyas-goenka 427ae3b
minor rename to type
shreyas-goenka 818f0df
Merge remote-tracking branch 'origin' into generate-required-v3
shreyas-goenka bcb614e
Validate required bundle fields
shreyas-goenka 0c988db
additional validation things
shreyas-goenka 539bd71
again
shreyas-goenka 5c8d934
-
shreyas-goenka e4124ae
-
shreyas-goenka 6ed0868
deterministic output
shreyas-goenka 7516ec1
deterministic output
shreyas-goenka 126dfb8
-gs
shreyas-goenka 1ab0efb
Add benchmark
shreyas-goenka 3607bb7
add more benchmarks
shreyas-goenka b112506
lint
shreyas-goenka 5c85284
baseline
shreyas-goenka b95da1b
refactor
shreyas-goenka b405af6
more efficient validation
shreyas-goenka 578112a
update the PR with latest changes
shreyas-goenka 7612cf9
lint
shreyas-goenka fbffb58
merge
shreyas-goenka 159333e
update acc tests
shreyas-goenka 2c68220
revert node test
shreyas-goenka e12d8f2
fix tests
shreyas-goenka 93ca657
lint
shreyas-goenka 2229963
typo
shreyas-goenka b4e1596
add empty case
shreyas-goenka 6e9988f
update test and make it better
shreyas-goenka 7031ce7
Merge remote-tracking branch 'origin' into validate-on-required
shreyas-goenka 8a7e423
update golden files
shreyas-goenka 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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.
Uh oh!
There was an error while loading. Please reload this page.
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.
This warning should not be there, actually. The whole 'schedule' field is cleared by dev mode and it's okay, not user's problem. However, in the current implementation it is set to null. That null should be treated as absence.
I noticed this because my PR improving null handling actually makes schedule disappear and that removes the warnings: https://github.com/databricks/cli/pull/3230/files#diff-18b1807771a343c3d7e7c543232e7ec53637f4a65b1191ab04becc7706b5fcd5L3
However, we should probably look into fixing null handling in required logic specifically. It may also come from other places.
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.
That seems like a mistake if this is a field that is required by the API. Does the API succeed even if this field is missing?