Cacher is the code snippet organizer for pro developers

## Technical Documentation
[Google](http://www.google.com)

=TEXTJOIN(":",1,MID(J8,SEQUENCE(6,1,1,2),2))

## Queues Section Explained

### Let's add detailed comments to the Queues section:

```yaml
# ========== QUEUES ==========
# SQS queues for asynchronous processing
# Decouples API from heavy processing tasks

RegistrationQueue:
  Type: AWS::SQS::Queue
  Properties:
    QueueName: !Sub "${AWS::StackName}-registrations"
    
    # How long a message stays invisible after pickup
    VisibilityTimeout: 60  # 60 seconds to process
    
    # Failed message handling
    RedrivePolic

## Storage Section Explained

### Let's add detailed comments to the Storage section:

```yaml
# ========== STORAGE ==========
# S3 bucket for storing event images, reports, and files
# Object storage service - like a cloud file system

ImagesBucket:
  Type: AWS::S3::Bucket
  Properties:
    # Globally unique name (includes account ID)
    BucketName: !Sub "${AWS::StackName}-images-${AWS::AccountId}"
    
    # Security: Block ALL public access by default
    PublicAccessBlockCon

## Databases Section Explained

### Let's add detailed comments to the Databases section:

```yaml
# ========== DATABASES ==========
# DynamoDB tables for storing application data
# NoSQL, serverless, auto-scaling databases

EventsTable:
  Type: AWS::DynamoDB::Table
  Properties:
    TableName: !Sub "${AWS::StackName}-events"
    
    # Pay only for what you use (no idle charges)
    BillingMode: PAY_PER_REQUEST
    
    # Define the attributes used in keys/indexes
    Attribut

## API Gateway Explained

### Let's add detailed comments to the API Gateway section:

```yaml
# ========== API GATEWAY ==========
# The "front door" for all your HTTP requests
# Routes requests to the right Lambda functions

ApiGateway:
  Type: AWS::Serverless::Api
  Properties:
    StageName: Prod              # Environment (Prod/Dev/Test)
    
    Auth:
      # By default, ALL endpoints require authentication
      DefaultAuthorizer: CognitoAuthorizer
      
      Authorizer

## Authentication Components Explained

### Let's add detailed comments to the Authentication section:

```yaml
# ========== AUTHENTICATION ==========
# This section handles user management and authentication
# Using AWS Cognito - a managed authentication service

UserPool:
  Type: AWS::Cognito::UserPool
  Properties:
    UserPoolName: !Sub "${AWS::StackName}-users"  # Unique pool name
    
    # Email will be automatically verified when users sign up
    AutoVerifiedAttributes:

/**
 * Calculates the number of valid original strings Alice might have typed.
 *
 * @param {string} word - The displayed string with potentially repeated characters.
 * @param {number} k - Minimum allowed length for the original string.
 * @return {number} - Count of possible original strings modulo 1e9 + 7.
 */
var possibleStringCount = function (word, k) {
    const MOD = 1e9 + 7;

    // Step 1: Run-Length Encoding — group consecutive identical characters
    const groups = [];
    let count

connect()
{
  
}

Connect1()
{
  
}

ë necessário quando usamos o procecesso dentro de algum job

BEGIN
      wwv_flow_api.set_security_group_id;
END;

```
https://admin.shopify.com/store/XXX/shop.json
```

Here's the syntax, **be wary of the fact that you can only pass ONE FILE to `-e`**

```bash
sam local invoke <FunctionName> -e <path/to/event.json>
```

For multiple events, run multiple times:
```bash
sam local invoke ImageProcessorFunction -e events/image-event.json
sam local invoke ImageProcessorFunction -e events/another-event.json
```

## S3 Event JSON Structure Explained

### The Event Anatomy

```json
{
  "Records": [        // Always an array - S3 can batch multiple events
    {
      "eventName": "ObjectCreated:Put",  // What happened
      "s3": {
        "bucket": {
          "name": "my-test-bucket"       // Which bucket
        },
        "object": {
          "key": "photos/vacation.jpg",   // File path/name
          "size": 2048576                 // Size in bytes (2MB)
        }
      }
    }
  ]

Nur so ein Gedanke: In logs haben wir gesehen, dass aufgrund von Connection Error in Alfa der Workflow LER nicht angetriggert werden konnte. Der Workflow LER ist aber schon ein Error Workflow. Heißt es, selbst ohne Connection Error würde die Buchung in Alfa sowieso nicht gebucht?
Antwort:
Ja, wenn der Webservice keine Connection aufbauen konnte, kann auch keine Buchung erstellt werden. Daher kam es überhaupt zum LER -> sollte also vorher schon der gleiche Fehler beim WS-Call saveThirdPartyAdhocC

*.pyc
/.venv/

### What We're Building

Instead of mocking, we'll run a **real DynamoDB** on your laptop using Docker. Think of it as a mini-AWS on your machine!

### Step 1: Start DynamoDB Local

```bash
# Pull and run DynamoDB Local in Docker
docker run -d -p 8000:8000 --name dynamodb-local amazon/dynamodb-local
```

**What this does:**
- `-d` = Run in background (detached)
- `-p 8000:8000` = Connect port 8000 on your laptop to the container
- `--name dynamodb-local` = Give it a friendly name