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

Add package scripts warning back #1764

Merged
merged 2 commits into from
Oct 23, 2024

Conversation

sfc-gh-melnacouzi
Copy link
Contributor

Pre-review checklist

  • I've confirmed that instructions included in README.md are still correct after my changes in the codebase.
  • I've added or updated automated unit tests to verify correctness of my new code.
  • I've added or updated integration tests to verify correctness of my new code.
  • I've confirmed that my changes are working by executing CLI's commands manually on MacOS.
  • I've confirmed that my changes are working by executing CLI's commands manually on Windows.
  • I've confirmed that my changes are up-to-date with the target branch.
  • I've described my changes in the release notes.
  • I've described my changes in the section below.

Changes description

Add package scripts warning back.
It disappeared due to the conversion of package scripts to post deploy scripts.

@@ -103,7 +103,7 @@ def test_sql_templating_emits_counter(
CLICounterField.TEMPLATES_PROCESSOR: 0,
CLICounterField.PDF_TEMPLATES: 1,
CLICounterField.POST_DEPLOY_SCRIPTS: 1,
CLICounterField.PACKAGE_SCRIPTS: 0,
CLICounterField.PACKAGE_SCRIPTS: 1,
Copy link
Contributor Author

Choose a reason for hiding this comment

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

test files have package scripts, so this should be 1.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we want to make the distinction that since the pdf is v1, then POST_DEPLOY_SCRIPTS should count as 0 then?

Copy link
Contributor Author

@sfc-gh-melnacouzi sfc-gh-melnacouzi Oct 22, 2024

Choose a reason for hiding this comment

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

i think it's something we can distinguish in the graphs themselves (like exclude package_scripts = 1). I do not want to touch the post_deploy_scripts part because the goal is to have the bulk part of the code operate in pdf v2 mode, and would make sense to keep the counters for this one with the post_deploy code itself.
It's basically a compromise.

@@ -115,7 +115,6 @@ def test_sql_templating_emits_counter(
CLICounterField.TEMPLATES_PROCESSOR: 0,
CLICounterField.PDF_TEMPLATES: 1,
CLICounterField.POST_DEPLOY_SCRIPTS: 1,
CLICounterField.PACKAGE_SCRIPTS: 0,
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 is PDF v2, so no need to emit metric for this one.

@sfc-gh-melnacouzi sfc-gh-melnacouzi merged commit f042ff0 into main Oct 23, 2024
21 checks passed
@sfc-gh-melnacouzi sfc-gh-melnacouzi deleted the melnacouzi-readd-package-scripts-warning branch October 23, 2024 13:42
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.

5 participants