propel_facets 0.1.3 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5f6199f2d9131858197a26b6c62314f6a8264c5d02e7cfec12259594e1729077
-  data.tar.gz: 92b2f2c5a2bad19c9a1aa864892289039ad7310e60c7180795a95d94e962c140
+  metadata.gz: e5233eaef1c8dc1acd2c631b9117c5b1a13c8deb1997d97a0e5fb294c7c55081
+  data.tar.gz: 15905b8628b5f2cb805b91ba4e25b36451a23ece1768216f64b0ae4fe964a96e
 SHA512:
-  metadata.gz: 51d9fcad6f5c127525d5134816b758400d67123966c2eb3200b05f35439494b1afb9d4caa552e6f2f1a53b7b61989038c66601b3f5f8d0c335bb5b4135f1705a
-  data.tar.gz: 36e97297e60bd7b27786a5be42ce46f3f840a920a0d9fae964d9a0806450c16135e2333f229d5e5c53414fed160d35f35e0ff40dd1176721cfd55eb4c9cf3353
+  metadata.gz: 57cf3b84754b71e1c18d45ac31690531ec212f49bc2179eda78fc3e791b01f0e6cf7c2dbf38f99e42765c45dfd1a39b071446a461ceb88a206339f2303a7ac82
+  data.tar.gz: 461b058e8e4f91e575d83560029b738f873c8dd85744be9c22e1bfd343a8c07b53cf1035229ea0906125c8710c20995c51e4f3c4ed568b408f047e2ca816b6e7

data/CHANGELOG.md

@@ -7,12 +7,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-### Added
-- **Clean controller generation by default** - PropelFacets controller templates now generate production-ready code
-  - Usage comments removed from default controller templates
-  - `--with-comments` flag available for learning/tutorial mode
-  - Improves integration with PropelApi generators
-
 ### Planned Features
 - Caching system integration with Rails caching (Solid Cache support)
 - Automatic association inclusion configuration
@@ -20,6 +14,38 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Metadata inclusion (pagination, counts, etc.)
 - Performance logging and optimization tools
 
+## [0.2.0] - 2025-09-02
+
+### Added
+- **Enhanced facet pattern consistency** - Standardized JSON facet definitions across all models
+  - Support for comprehensive User model facets with authentication fields
+  - Improved association handling in facet rendering with proper include directives
+  - Consistent field inclusion patterns for better API consistency
+
+### Improved
+- **Compatibility updates** - Enhanced integration with PropelAuthentication 0.2.0 and PropelApi 0.2.0
+  - Updated to work with new security-first architecture
+  - Maintained full compatibility with enhanced JSON facet definitions
+  - Support for `PropelAuthenticationConcern` namespace changes
+  - Seamless integration with configurable tenancy requirements
+
+### Fixed
+- **JSON facet rendering** - Enhanced association handling and field inclusion
+  - Proper handling of organization associations in User model facets
+  - Consistent foreign key and association rendering across all model types
+
+## [0.1.4] - 2025-08-15
+
+### Added
+- **Clean controller generation by default** - PropelFacets controller templates now generate production-ready code
+  - Usage comments removed from default controller templates
+  - `--with-comments` flag available for learning/tutorial mode
+  - Improves integration with PropelApi generators
+
+### Fixed
+- **Generator extraction system** - Core infrastructure files now properly extracted during installation
+- **Standalone operation** - Complete "no black box" policy implementation
+
 ## [0.1.0] - 2025-01-XX
 
 ### Added

data/better_nesting.md

@@ -0,0 +1,166 @@
+# Feature Implementation Guide: Per-Association Facet Specification in json_facet includes
+
+## Current State
+The `json_facet` system currently supports including associations, but all included associations use the same facet determined by the `include_as` parameter:
+
+```ruby
+# Current syntax - all associations use :included facet
+json_facet :details, 
+  fields: [:id, :name], 
+  include: [:organization, :user, :comments], 
+  include_as: :included
+```
+
+## Desired Feature
+Enable specifying different facets for different associations within a single json_facet definition:
+
+```ruby
+# Proposed syntax - each association can specify its own facet
+json_facet :details,
+  fields: [:id, :name],
+  include: {
+    organization: :short,      # Use organization's :short facet
+    user: :included,          # Use user's :included facet  
+    comments: :minimal        # Use comment's :minimal facet
+  }
+```
+
+## Implementation Approach
+
+### 1. Modify `json_facet` method (line 74-85)
+- Detect when `include` is a Hash vs Array
+- Parse Hash format to extract association → facet mappings
+- Maintain backward compatibility with Array format
+
+### 2. Update `facet_serializable_options` method (line 154-161)
+Current code:
+```ruby
+include = actual[:include].reduce({}) do |memo, current|
+  memo.update(current => { facet: include_as })  # Same facet for all
+end
+```
+
+New logic needed:
+```ruby
+include = actual[:include].reduce({}) do |memo, current|
+  if current.is_a?(Hash)
+    # Handle { association: :facet_name } format
+    current.each do |assoc, facet|
+      memo.update(assoc => { facet: facet })
+    end
+  else
+    # Backward compatibility: use include_as for array format
+    memo.update(current => { facet: include_as })
+  end
+  memo
+end
+```
+
+### 3. Mixed Syntax Support
+Support combining both syntaxes in one facet:
+```ruby
+json_facet :details,
+  include: [:tags, { organization: :short, user: :minimal }],
+  include_as: :included  # Default for array items
+```
+
+### 4. Validation & Error Handling
+- Validate that specified facets exist on target models
+- Provide meaningful error messages for missing facets
+- Handle edge cases (nil facets, invalid association names)
+
+## Example Usage Patterns
+
+### Basic Usage
+```ruby
+class Product < ApplicationRecord
+  json_facet :api_response,
+    fields: [:id, :name, :price],
+    include: {
+      category: :short,        # Just id, name  
+      reviews: :summary,       # rating, comment excerpt
+      seller: :public         # name, avatar, rating
+    }
+end
+```
+
+### Mixed with Array Syntax
+```ruby
+class BlogPost < ApplicationRecord  
+  json_facet :feed_item,
+    fields: [:id, :title, :excerpt],
+    include: [
+      :tags,                   # Use default :included facet
+      { author: :author_card } # Use custom :author_card facet
+    ],
+    include_as: :included      # Default for array items
+end
+```
+
+### Nested Facet Chains
+```ruby
+class User < ApplicationRecord
+  json_facet :profile,
+    fields: [:id, :username],
+    include: {
+      organization: :public,   # Organization uses its :public facet
+      posts: :feed_summary     # Posts use their :feed_summary facet  
+    }
+end
+
+class Organization < ApplicationRecord
+  json_facet :public,
+    fields: [:id, :name, :logo],
+    include: { industry: :basic }  # Nested includes work too
+end
+```
+
+## Backward Compatibility Requirements
+- Existing `include: [:association]` syntax must continue working
+- Current `include_as: :facet` behavior must remain unchanged for array includes
+- No breaking changes to existing APIs
+
+## Test Cases to Implement
+
+### 1. Basic Hash Syntax
+```ruby
+test "should support hash syntax for per-association facets" do
+  # Test that each association uses its specified facet
+end
+```
+
+### 2. Backward Compatibility
+```ruby
+test "should maintain array syntax compatibility" do
+  # Ensure existing code continues working
+end
+```
+
+### 3. Mixed Syntax
+```ruby 
+test "should support mixed array and hash syntax" do
+  # Test combining both syntaxes in one facet
+end
+```
+
+### 4. Error Handling
+```ruby
+test "should handle missing facets gracefully" do
+  # Test behavior when specified facet doesn't exist
+end
+```
+
+### 5. Deep Nesting
+```ruby
+test "should support nested facet chains" do
+  # Test that included objects can have their own includes
+end
+```
+
+## Implementation Priority
+1. **Phase 1**: Basic Hash syntax support
+2. **Phase 2**: Mixed Array/Hash syntax  
+3. **Phase 3**: Advanced validation and error handling
+4. **Phase 4**: Performance optimization for complex nested includes
+
+This feature would provide much more granular control over JSON serialization while maintaining the elegant declarative syntax that makes json_facet powerful.

data/lib/generators/propel_facets/templates/models/application_record.rb

@@ -10,4 +10,10 @@ class ApplicationRecord < ActiveRecord::Base
   json_facet :included, base: :reference
   json_facet :short, base: :included, include_as: :reference
   json_facet :details, base: :short, include_as: :included
+
+  # Organization scoping for multi-tenancy
+  scope :for_organization, ->(organization_id) {
+    return none if organization_id.blank?
+    where(organization_id: organization_id)
+  }
 end 

data/lib/propel_facets.rb

@@ -1,3 +1,3 @@
 module PropelFacets
-  VERSION = "0.1.3"
+  VERSION = "0.2.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: propel_facets
 version: !ruby/object:Gem::Version
-  version: 0.1.3
+  version: 0.2.0
 platform: ruby
 authors:
 - Propel Team
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2025-07-22 00:00:00.000000000 Z
+date: 2025-09-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -43,6 +43,7 @@ files:
 - LICENSE
 - README.md
 - Rakefile
+- better_nesting.md
 - lib/generators/propel_facets/README.md
 - lib/generators/propel_facets/USAGE
 - lib/generators/propel_facets/install_generator.rb