cmdx-i18n 0.2.0 → 2.0.0

data/lib/locales/zh-YUE.yml

@@ -1,15 +1,15 @@
 zh-YUE:
   cmdx:
     attributes:
-      required: "必須可以通過來源存取"
-      undefined: "委託畀未定義嘅方法 %{method}"
+      required: "係必要嘅"
     coercions:
       into_a: "無法強制轉換成 %{type}"
       into_an: "無法強制轉換成 %{type}"
       into_any: "無法強制轉換成其中一個：%{types}"
-      unknown: "未知嘅 %{type} 強制轉換類型"
-    faults:
-      unspecified: "冇提供原因"
+    reasons:
+      unspecified: "未指定"
+    outputs:
+      missing: "必須喺上下文入面設定"
     types:
       array: "陣列"
       big_decimal: "大十進位"
@@ -25,6 +25,7 @@ zh-YUE:
       symbol: "符號"
       time: "時間"
     validators:
+      absence: "必須係空白"
       exclusion:
         of: "唔可以係其中一個：%{values}"
         within: "唔可以喺 %{min} 同 %{max} 之間"
@@ -37,6 +38,9 @@ zh-YUE:
         is_not: "長度唔可以係 %{is_not}"
         min: "長度至少必須係 %{min}"
         max: "長度最多可以係 %{max}"
+        gt: "長度必須大過 %{gt}"
+        lt: "長度必須細過 %{lt}"
+        nil_value: "必須有長度"
         not_within: "長度唔可以喺 %{min} 同 %{max} 之間"
         within: "長度必須喺 %{min} 同 %{max} 之間"
       numeric:
@@ -44,6 +48,9 @@ zh-YUE:
         is_not: "唔可以係 %{is_not}"
         min: "至少必須係 %{min}"
         max: "最多可以係 %{max}"
+        gt: "必須大過 %{gt}"
+        lt: "必須細過 %{lt}"
+        nil_value: "必須係數字"
         not_within: "唔可以喺 %{min} 同 %{max} 之間"
         within: "必須喺 %{min} 同 %{max} 之間"
       presence: "唔可以係空白"

data/src/cmdx-logo.svg

@@ -0,0 +1 @@
+<svg width="352.2" height="112.266" viewBox="0 0 203 64.708" xmlns="http://www.w3.org/2000/svg" xmlSpace="preserve"><path d="M172.908 17.723 169.4 23.17 156.385 3.323h3.507l9.508 14.77 1.938-3.139L161.738 0h-11.446L169.4 29.262 188.046 0h-3.97L173 17.54zm-20.677 43.57h-3.139l18.646-29.447L147.431.093h-3.97l20.308 31.846L143 64.708l10.985-.092 39.138-61.2h3.323L174.57 37.754l13.662 21.415h3.969l-13.754-21.415L202.538.093H191.37zm29.63-23.262 15.047 23.262h-10.523l-13.662-20.77-15.508 24.093h3.97l11.63-18 11.723 18H203l-18.83-29.262-.278-.461z" fill="#fe1817"/><path d="M41.667 14v12.8h-23.42c-3.214.272-5.665 3.05-5.665 6.318s2.45 5.937 5.664 6.318H33.17v4.248H18.246a10.65 10.65 0 0 1-9.858-10.62c0-5.447 4.194-10.077 9.64-10.512h19.39v-4.303H18.246v.054A14.823 14.823 0 0 0 4.248 33.118c0 7.898 6.21 14.38 13.998 14.815h19.172v-8.497h4.249v12.745h-23.42A19.063 19.063 0 0 1 0 33.118a19.033 19.033 0 0 1 18.246-19.063zM75 35.623 87.2 14h13.508v38.181H87.963v-14.27l-8.116 14.27h-9.749L57.734 30.504v-8.007l14.87 25.436h4.792l14.815-25.436v25.436h4.249V18.249H89.65l-14.76 25.49-14.542-25.49H53.54v29.684h4.194v-8.007l4.249 7.299v4.956H49.292v-38.18H62.8zM108.333 14h23.42C141.94 14.436 150 22.824 150 33.064c0 10.294-8.061 18.681-18.246 19.117h-23.42V22.497h23.42a10.65 10.65 0 0 1 9.858 10.621c0 5.447-4.194 10.13-9.64 10.566H116.83V30.286h4.248v9.15l10.676-.054c3.213-.273 5.664-3.05 5.664-6.264 0-2.778-1.743-5.065-4.194-5.991-.926-.382-1.47-.382-2.94-.382h-17.702v21.188h19.172a14.84 14.84 0 0 0 13.998-14.87c0-7.897-6.21-14.379-13.998-14.814h-23.42z"/></svg>

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: cmdx-i18n
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 2.0.0
 platform: ruby
 authors:
 - Juan Gomez
@@ -15,28 +15,14 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 1.5.1
+        version: 2.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 1.5.1
-- !ruby/object:Gem::Dependency
-  name: zeitwerk
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
+        version: 2.0.0
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
@@ -156,11 +142,6 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".cursor/prompts/docs.md"
-- ".cursor/prompts/llms.md"
-- ".cursor/prompts/rspec.md"
-- ".cursor/prompts/yardoc.md"
-- ".cursor/rules/cursor-instructions.mdc"
 - ".irbrc"
 - ".rspec"
 - ".rubocop.yml"
@@ -260,7 +241,9 @@ files:
 - lib/locales/zh-HK.yml
 - lib/locales/zh-TW.yml
 - lib/locales/zh-YUE.yml
-- src/cmdx-i18n-logo.png
+- src/cmdx-dark-logo.png
+- src/cmdx-light-logo.png
+- src/cmdx-logo.svg
 homepage: https://github.com/drexed/cmdx-i18n
 licenses:
 - MIT
@@ -278,14 +261,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 3.1.0
+      version: 3.3.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.7.1
+rubygems_version: 4.0.10
 specification_version: 4
 summary: I18n translations and localization for CMDx.
 test_files: []

data/.cursor/prompts/docs.md

@@ -1,12 +0,0 @@
-You are a senior Ruby developer with expert knowledge of CMDx and writing documentation.
-
-Update the active tab using the following guidelines:
-
-- Follow best practices and implementation
-- Use a consistent professional voice
-- Examples should be concise, non-repetitive, and realistic
-- Update any pre-existing documentation to match stated rules
-- Examples should not cross boundaries or focus
-- Docs must cover both typical use cases, including invalid inputs and error conditions
-- Use GitHub flavored markdown, including alerts to emphasize critical information (https://github.com/orgs/community/discussions/16925)
-- Optimize for LLM's including coding and AI agents

data/.cursor/prompts/llms.md

@@ -1,20 +0,0 @@
-Process the following instructions in the order given:
-
-1. Create an `LLM.md` file
-2. Append all files within `docs/**/*.md` into @LLM.md
-  2a. Use order outlined in the table of contents of @README.md
-  2b. Process one file at a time faster performance and improved accuracy
-  2c. Remove the table of contents from the chunk
-  2c. Remove the navigations below `---` from the chunk
-  2d. Wrap the chunk the files GitHub url the top and a spacer at the bottom like so:
-      ```
-
-      ---
-      url: https://github.com/drexed/cmdx/blob/main/docs/callbacks.md
-      ---
-
-      {{ chunk }}
-
-      ---
-
-      ```

data/.cursor/prompts/rspec.md

@@ -1,24 +0,0 @@
-You are a senior Ruby developer with expert knowledge of RSpec.
-
-Add tests for the active tab using the following guidelines:
-
-- Expectations should be concise, non-repetitive, and realistic (how it would be used in the real world)
-- Follow best practices and implementation
-- Update any pre-existing specs to match stated rules
-- New tests should be consistent with current `spec/cmdx` specs
-- Use custom matchers available within `lib/cmdx/rspec`
-- Use task helpers available within `spec/support/helpers`
-- Use stubs to return predefined values for specific methods. Isolate the unit being tested, but avoid over-mocking; test real behavior when possible (mocks should be used only when necessary)
-- Ensure each test is independent; avoid shared state between tests
-- Use let and let! to define test data, ensuring minimal and necessary setup
-- Context block descriptions should start with the following words: `when`, `with`, `without`
-- Organize tests logically using describe for classes/modules and context for different scenarios
-- Use subject to define the object under test when appropriate to avoid repetition
-- Ensure test file paths mirror the structure of the files being tested, but within the spec directory (e.g., lib/cmdx/task.rb → spec/cmdx/task_spec.rb)
-- Use clear and descriptive names for describe, context, and it blocks
-- Prefer the expect syntax for assertions to improve readability
-- Keep test code concise; avoid unnecessary complexity or duplication
-- Tests must cover both typical cases and edge cases, including invalid inputs and error conditions
-- Consider all possible scenarios for each method or behavior and ensure they are tested
-- Do NOT include integration or real world examples
-- Verify all specs are passing

data/.cursor/prompts/yardoc.md

@@ -1,14 +0,0 @@
-You are a senior Ruby developer with expert knowledge of YARDoc.
-
-Add yardoc to the active tab using the following guidelines:
-
-- Follow best practices and implementation
-- New documentation should be consistent with current `lib/cmdx` documentation
-- Examples should be concise, non-repetitive, and realistic
-- Avoid unnecessary complexity or duplication
-- Update any pre-existing documentation to match stated rules
-- Do NOT include `CMDx` module level docs
-- Module level docs description should NOT include `@example`
-- Method level docs should include `@example`, `param`, `@options`, `@return`, and any `@raise`
-- Hash `@params` should expand with possible `@option`
-- Module and method level docs should NOT include `@since`

data/.cursor/rules/cursor-instructions.mdc

@@ -1,61 +0,0 @@
----
-description:
-globs:
-alwaysApply: true
----
-
-# Ruby Coding Standards
-
-Follow the official Ruby gem guides for best practices.
-Reference the guides outlined in https://guides.rubygems.org
-
-## Project Context
-CMDx::I18n is a collection of localized translations for the CMDx framework.
-Reference the CMDx documentation in https://github.com/drexed/cmdx/blob/main/LLM.md
-
-## Technology Stack
-- Ruby 3.4+
-- RSpec 3.1+
-- CMDx 1.6+
-
-## Code Style and Structure
-- Write concise, idiomatic Ruby code with accurate examples
-- Follow Ruby conventions and best practices
-- Use object-oriented and functional programming patterns as appropriate
-- Prefer iteration and modularization over code duplication
-- Use descriptive variable and method names (e.g., user_signed_in?, calculate_total)
-- Write comprehensive code documentation using the Yardoc format
-
-## Naming Conventions
-- Use snake_case for file names, method names, and variables
-- Use CamelCase for class and module names
-
-## Syntax and Formatting
-- Follow the Ruby Style Guide (https://rubystyle.guide/)
-- Follow Ruby style conventions (2-space indentation, snake_case methods)
-- Use Ruby's expressive syntax (e.g., unless, ||=, &.)
-- Prefer double quotes for strings
-- Respect my Rubocop options
-
-## Performance Optimization
-- Use memoization for expensive operations
-
-## Testing
-- Follow the RSpec Style Guide (https://rspec.rubystyle.guide/)
-- Write comprehensive tests using RSpec
-- It's ok to put multiple assertions in the same example
-- Include both BDD and TDD based tests
-- Create test objects to share across tests
-- Do NOT make tests for obvious or reflective expectations
-- Prefer real objects over mocks. Use `instance_double` if necessary; never `double`
-- Don't test declarative configuration
-- Use appropriate matchers
-- Update tests and update Yardocs after you write code
-
-## Documentation
-- Utilize the YARDoc format when documenting Ruby code
-- Follow these best practices:
-  - Avoid redundant comments that merely restate the code
-  - Keep comments up-to-date with code changes
-  - Keep documentation consistent
-- Update CHANGELOG.md with any changes