@effect-aws/client-iot-wireless@1.9.0

Minor Changes

• #106 e07e3c0 Thanks @floydspace! - ## Refactored service configuration and layer management

  Since this version the effectful logger is not added into native AWS client constructor. Providing logger by default causes risk of logging sensitive information. The logger should be added explicitly by the choice of a user. It can be done by using extended logger option:

  import { DynamoDB } from "@effect-aws/client-dynamodb";
  
  // using default logger
  DynamoDB.layer({ logger: true });
  
  // or using custom logger (the same as default)
  DynamoDB.layer({
    logger: {
      trace: Effect.logTrace,
      debug: Effect.logDebug,
      info: Effect.logInfo,
      warn: Effect.logWarning,
      error: Effect.logError,
    },
  });
  
  // and you could remap logger methods as you want
  DynamoDB.layer({
    logger: {
      debug: Effect.logDebug,
      info: Effect.logDebug,
      warn: Effect.logWarning,
      error: Effect.logError,
    },
  });

  Additionally to that, the whole service configuration was refactored in better way, now it is not a strict layer dependency, but the global value which defaults to empty object. The global value can be configured by using the effect higher order function or the layer setter.

  import { DynamoDBServiceConfig } from "@effect-aws/client-dynamodb";
  
  // using effect higher order function
  DynamoDBServiceConfig.withDynamoDBServiceConfig({ logger: true });
  
  // or using layer setter
  Layer.provide(
    DynamoDBServiceConfig.setDynamoDBServiceConfig({ logger: true }),
  );

  Breaking changes

  This release is not a breaking change if you just use service methods and service layer, which in most cases should be the case.

  If you had to use custom configuration, you should update your code to use new configuration methods.

Patch Changes

• #106 e07e3c0 Thanks @floydspace! - drop support for effect version lower than 3.0.4

• Updated dependencies [e07e3c0, e07e3c0]:

  • @effect-aws/commons@0.1.0