Make
π Description
Generate various project files and components. The make command is the primary code generation tool in Gexd CLI, offering powerful scaffolding capabilities for Flutter projects with GetX and Clean Architecture patterns.
βοΈ Usage
π Available Subcommands
ποΈ Core Components
Description: Generate complete screen components (controller, view, binding)
Description: Generate controller files for state management
Description: Generate view files (UI components)
Description: Generate binding files for dependency injection
π Data Layer
Description: Generate type-safe model files from JSON sources with advanced features
Description: Generate repository files for data access layers
Description: Generate service files for business logic
Description: Generate provider files for data sources
ποΈ Architecture Components
Description: Generate entity files for domain layer
Description: Generate interface files for contracts and abstractions
Description: Generate custom exception classes
Description: Generate middleware files for request/response handling
π οΈ Utility Components
Description: Generate reusable widget components
Description: Generate utility helper classes
Description: Generate constant definition files
π― Command Categories
π± UI Components
screen- Complete screen with controller, view, bindingview- UI view componentswidget- Reusable widget components
π§ State Management
controller- State controllersbinding- Dependency injection bindingsmiddleware- Request/response middleware
π Data Management
model- Data models with serializationrepository- Data access repositoriesservice- Business logic servicesprovider- Data source providers
ποΈ Architecture
entity- Domain entitiesinterface- Contract abstractionsexception- Custom exceptions
π οΈ Utilities
util- Helper utilitiesconstant- Application constants
π Common Usage Patterns
π± Complete Feature Generation
ποΈ Clean Architecture Setup
π API Integration Workflow
βοΈ Global Options
Most make subcommands support these common options:
π Organization
--on <path>- Specify subdirectory for generated files--force- Force overwrite existing files without prompting
π¨ Customization
--type <type>- Specify component type/style--template <template>- Choose generation template--style <style>- Select code generation style
π§ Features
--interface- Generate with interface abstraction--immutable- Create immutable data structures--copyWith- Add copy methods for state updates
π‘ Pro Tips
π― Best Practices
Start with Architecture: Generate entities and interfaces first
Use
--onfor Organization: Keep related files in subdirectoriesEnable Interfaces: Use
--interfacefor better testabilityForce During Development: Use
--forcefor rapid iteration
π Efficiency Tips
Batch Generation: Generate related components together
Template Reuse: Save commonly used flag combinations
API-First Development: Generate models from live APIs
Relationship Management: Use
--relationships-in-folderfor complex models
π§ Advanced Workflows
Feature-Based: Group components by feature using
--onLayer-Based: Organize by architectural layers
Test-Driven: Generate interfaces first for better testing
Iterative: Start simple, add features with
--force
π Documentation Links
For detailed documentation on each subcommand, click the links above or visit:
Screen Command - Complete UI component generation
Model Command - Advanced data model creation
Repository Command - Data access layer patterns
Service Command - Business logic organization
Widget Command - Reusable UI components
Generated automatically by gexd_doc
Last updated