Harrier Open Standards
CtrlK
  • Open Standards
  • Technical
    • Best Practices
      • Naming conventions
        • Object / Metadata Type / Settings Conventions
        • Custom Permissions Conventions
        • Profile Conventions
        • Permission Set (Group) Conventions
      • Salesforce Project Structure
      • Apex Style Guide
      • Development Principles
      • Apex Unit Testing Guidelines
      • Feature flags
    • Documentation
      • GPT Instructions
    • Frameworks
      • flxbl - Continuous Delivery
      • fflib - Apex Framework
      • Nebula Logger - Logging
    • Integration Strategies
      • Data warehouse & Reverse ETL
    • Development & Deployment Strategies
  • Functional
    • Requirement definition
      • GPT Instructions
    • Documentation
Powered by GitBook
On this page
  • Links
  • Use case
  • Rationale
  • Alternatives

Was this helpful?

  1. Technical
  2. Frameworks

fflib - Apex Framework

Links

Description
Url

main

https://github.com/apex-enterprise-patterns - fflib-apex-mocks https://github.com/apex-enterprise-patterns - fflib-apex-common

extensions

https://github.com/wimvelzeboer/fflib-apex-extensions

template generator

https://github.com/wimvelzeboer/fflib-templates (beta version)

Use case

TO DO: Write out what use case this framework seeks to address.

Rationale

Usage of fflib encourages the developer to use Separation of Concerns, DRY, SOLID and Dependency Injection design principals. This helps to create code that is readable for other developers that haven't worked with the code before.

Alternatives

Previousflxbl - Continuous DeliveryNextNebula Logger - Logging

Last updated 29 days ago

Was this helpful?