Skip to content
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

Fix config targets #1673

Merged
merged 3 commits into from
Feb 7, 2024
Merged

Fix config targets #1673

merged 3 commits into from
Feb 7, 2024

Conversation

Ekrekr
Copy link
Contributor

@Ekrekr Ekrekr commented Feb 6, 2024

No description provided.

@Ekrekr Ekrekr requested a review from BenBirt February 6, 2024 15:11
Copy link
Collaborator

@BenBirt BenBirt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll be honest, I am very confused about the current state of table.ts and friends. But the tests are passing, and presumably we can always clean up / refactor later.

core/utils.ts Outdated
Comment on lines 263 to 265
name: actionConfigTarget.name,
schema: actionConfigTarget.dataset,
database: actionConfigTarget.project
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...actionConfigTarget

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would add the dataset and project fields to the proto object, which even though they're not fields, is valid in protobufjs objects


const result = runMainInVm(coreExecutionRequestFromPath(projectDir));

expect(result.compile.compiledGraph.graphErrors.compilationErrors).deep.equals([]);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems like a pretty weak assertion - dependency targets could be completely ignored by compilation, and this would still be true

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have added more tests

@Ekrekr
Copy link
Contributor Author

Ekrekr commented Feb 7, 2024

I'll be honest, I am very confused about the current state of table.ts and friends. But the tests are passing, and presumably we can always clean up / refactor later.

The class constructor is the builder for action configs - it's large at the moment because I want to split out view and incrementalTable into separate classes (soon).

@Ekrekr Ekrekr merged commit 994203b into main_v3 Feb 7, 2024
4 checks passed
@Ekrekr Ekrekr deleted the fix-config-targets branch February 7, 2024 15:48
moker-spaghetti pushed a commit to moker-spaghetti/dataform that referenced this pull request May 26, 2024
* Fix config targets

* Fix lint

* Add more tests, fix fully qualified dependencies for notebooks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants