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: revert "chore: rename Lambda related interfaces (#288)" #296

Merged
merged 1 commit into from
Sep 9, 2024

Conversation

lym953
Copy link
Contributor

@lym953 lym953 commented Sep 9, 2024

What does this PR do?

Reverts #288

Motivation

#294

Testing Guidelines

for Python

Steps
  1. Make changes on the example Python stack to make it use DatadogProps 480eed0
  2. Deploy the stack
Result

Before:

  • cdk deploy gives an error:

ImportError: cannot import name 'DatadogProps' from 'datadog_cdk_constructs_v2'

After:

  • cdk deploy runs successfully

for Go

Similar. Reproduced the issue on v1.16.0, and ensure the issue is fixed by the PR.

Additional Notes

Types of Changes

  • Bug fix
  • New feature
  • Breaking change
  • Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

  • This PR's description is comprehensive
  • This PR contains breaking changes that are documented in the description
  • This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
  • This PR impacts documentation, and it has been updated (or a ticket has been logged)
  • This PR's changes are covered by the automated tests
  • This PR collects user input/sensitive content into Datadog

constructor(scope: Construct, id: string, props: DatadogLambdaProps) {
if (process.env.DD_CONSTRUCT_DEBUG_LOGS?.toLowerCase() === "true") {
constructor(scope: Construct, id: string, props: DatadogProps) {
if (process.env.DD_CONSTRUCT_DEBUG_LOGS?.toLowerCase() == "true") {

Choose a reason for hiding this comment

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

Code Quality Violation

Suggested change
if (process.env.DD_CONSTRUCT_DEBUG_LOGS?.toLowerCase() == "true") {
if (process.env.DD_CONSTRUCT_DEBUG_LOGS?.toLowerCase() === "true") {
Expected '===' and instead saw '=='. (...read more)

In JavaScript, == and != comparisons do type coercion, which can be confusing and may introduce potential errors. Use the type-safe equality operators === and !== instead.

View in Datadog  Leave us feedback  Documentation

constructor(scope: Construct, id: string, props: DatadogLambdaProps) {
if (process.env.DD_CONSTRUCT_DEBUG_LOGS?.toLowerCase() === "true") {
constructor(scope: Construct, id: string, props: DatadogProps) {
if (process.env.DD_CONSTRUCT_DEBUG_LOGS?.toLowerCase() == "true") {

Choose a reason for hiding this comment

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

Code Quality Violation

Suggested change
if (process.env.DD_CONSTRUCT_DEBUG_LOGS?.toLowerCase() == "true") {
if (process.env.DD_CONSTRUCT_DEBUG_LOGS?.toLowerCase() === "true") {
Expected '===' and instead saw '=='. (...read more)

In JavaScript, == and != comparisons do type coercion, which can be confusing and may introduce potential errors. Use the type-safe equality operators === and !== instead.

View in Datadog  Leave us feedback  Documentation

@lym953 lym953 marked this pull request as ready for review September 9, 2024 21:34
@lym953 lym953 requested a review from a team as a code owner September 9, 2024 21:34
@lym953
Copy link
Contributor Author

lym953 commented Sep 9, 2024

/merge

@dd-devflow
Copy link

dd-devflow bot commented Sep 9, 2024

🚂 MergeQueue: pull request added to the queue

The median merge time in main is 4m.

Use /merge -c to cancel this operation!

@dd-mergequeue dd-mergequeue bot merged commit 0330420 into main Sep 9, 2024
15 checks passed
@dd-mergequeue dd-mergequeue bot deleted the yiming.luo/revert-interface-renaming branch September 9, 2024 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants