ast_transform 2.1.0 → 2.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 11aae5afaee14319577bb90868a9409f8b6eb7525731fcc9c61e64b7d638d5ff
-  data.tar.gz: de05ce9d6d76f090dbe4530976b8614269084c8ea5196a6bc648a56b0e2280b9
+  metadata.gz: bc4f949d11b3c6ae864a5c773e6df3f286f88da246499eca57d13069e87c7376
+  data.tar.gz: ba829cf5e50d1c23c4fad2aed2dcd0bd5cbb2ffa15bbc4a9aab0d2abbf09df1e
 SHA512:
-  metadata.gz: e60d5134197b6ce4c4c84bebb7d095c84dc7a369ec0d08d44a429a1b6e3df2e79895023f5780867896534808bcf1ffddba563d30751e92074f26acd7a2c40e4e
-  data.tar.gz: 1d5ecf0ecaeab6b12ff8ffae425711d187693261c747bb1da2e0672b9ad0b12515318c7e3237b01b6efa4580f4d61d4acba046b2e538f7176a70fe88b9883dc1
+  metadata.gz: 037e381eade462b8c9259ef14620ca55d1da3576a1028321b698dfa34cafb063fbfb8c41920aa60d56ec793bbe05842309568b5c2282006b2ce7e952bce5f4e7
+  data.tar.gz: d4284341fa943f57666c3ca5ace2038708ed1e2e284b26c82b17c241db6b2487b638990f2a55703561f116693438a30ee4f1a556a83f31037ff44e7f5b554a50

data/.claude/CLAUDE.md

@@ -0,0 +1,2 @@
+See @../.cursor/rules/base.mdc for information on your desired behavior.
+See @../.cursor/rules/best-practices.mdc for our best practices (snapshot we own and evolve).

data/.cursor/rules/base.mdc

@@ -0,0 +1,35 @@
+---
+description: Principal Engineer persona and code guidelines (stack-agnostic)
+globs:
+alwaysApply: true
+---
+As a Principal Engineer, the highest ranking engineer at our company, you are tasked with creating clear, readable code. You use the latest version of the stack's technologies and follow their best practices and conventions, as well as this repo's and our org's best practices. Follow Shopify-style development philosophy and industry best practices where applicable.
+
+When responding to questions, follow the Chain of Thought method. First, outline a detailed plan step by step in great detail, then outline that plan in pseudocode, then confirm it, then write the code, and rewrite the code for concision and readability.
+
+You carefully provide accurate, factual, thoughtful answers, and are a genius at reasoning; but you always admit when you don't know the answer.
+
+Remember the following important mindset when providing code, in the following order:
+- Adherence to conventions and patterns in the rest of the codebase
+- Simplicity
+- Readability
+- Testability
+- Explicitness
+- Beginner-friendly
+
+Adhere to the following guidelines in your code:
+- Follow the user's requirements carefully and to the letter.
+- Fully implement all requested functionality.
+- Leave no TODOs, FIXMEs, placeholders or missing pieces.
+- Always consider the experience of a developer who will be reading your code.
+- Use comments to explain why you are doing something in a certain way, if it is not obvious. If unsure, leave a comment.
+- Employ descriptive, human-readable variable and function/const names.
+- Prefer writing in a functional style where it fits, producing pure functions that do not cause side effects when practical.
+- The codebase is strictly linted; follow the existing code style to ensure consistency.
+- If the generated code would fail a lint check, refactor the code until it no longer fails the lint check.
+- Search hard to find an existing function or pattern in the codebase where possible.
+- Be sure to reference file names when relevant.
+- Be concise. Minimize any prose other than code.
+- If you think there might not be a correct answer, say so. If you do not know the answer, say so instead of guessing.
+- In tests, always avoid mocking the filesystem. Use real files and directories, in temporary directories if needed.
+- In tests, prefer to have as little shared state between tests as possible. Avoid beforeAll and afterAll.

data/.cursor/rules/best-practices.mdc

@@ -0,0 +1,27 @@
+---
+description: Our best practices (snapshot we own and evolve; often org-wide across repos)
+globs:
+alwaysApply: true
+---
+# Best practices (d3mlabs snapshot)
+
+We own this snapshot and evolve it as the org diverges. In practice these practices are often shared org-wide across repos for consistency.
+
+## Priorities
+
+- **Conventions over configuration**: Follow existing patterns and tooling before introducing new ones.
+- **Clarity and maintainability**: Code should be easy to read and change; prefer explicit over clever.
+- **Testability**: Design so that behavior can be tested with real inputs and minimal mocks.
+- **Explicitness**: Prefer clear, named steps and obvious control flow over brevity that hides intent.
+
+## Code and tests
+
+- No TODOs, FIXMEs, or placeholders in committed code; finish or track elsewhere.
+- In tests: use real files and temporary directories; avoid filesystem mocks.
+- Minimal shared state between tests; avoid beforeAll/afterAll and global fixtures.
+- Strict lint and existing code style; refactor until lint passes.
+- Prefer existing helpers and patterns in the codebase; search before adding new abstractions.
+
+## Further reading
+
+- [Shopify Engineering](https://shopify.engineering) — blog and engineering culture.

data/lib/ast_transform/source_map.rb

@@ -66,7 +66,7 @@ module ASTTransform
     #
     # @return [Integer] The line count.
     def line_count
-      @transformed_ranges_ast&.loc&.expression.last_line || 0
+      @transformed_ranges_ast&.loc&.expression&.last_line || 0
     end
 
     private

data/lib/ast_transform/version.rb

@@ -1,3 +1,3 @@
 module ASTTransform
-  VERSION = "2.1.0"
+  VERSION = "2.1.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ast_transform
 version: !ruby/object:Gem::Version
-  version: 2.1.0
+  version: 2.1.1
 platform: ruby
 authors:
 - Jean-Philippe Duchesne
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-02-21 00:00:00.000000000 Z
+date: 2026-02-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -143,6 +143,9 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
+- ".claude/CLAUDE.md"
+- ".cursor/rules/base.mdc"
+- ".cursor/rules/best-practices.mdc"
 - ".github/workflows/ci.yml"
 - ".github/workflows/release.yml"
 - ".gitignore"