planned features added

Author: Kalybos

CHANGELOG.md

@@ -23,3 +23,9 @@
 - Refactored code structure for improved maintainability
 - Updated example package structure
 - Modified the env package generation's command
+
+## 1.1.3
+
+- `--output-dir`: Custom output directory (default: `env`)
+- `--no-encrypt`: Skip encryption of sensitive variables
+- `--verbose`: Detailed output during build process

README.md

@@ -26,12 +26,6 @@ Install the CLI globally using pub:
 dart pub global activate env_builder_cli
 ```
 
-Or using the executable name:
-
-```bash
-dart pub global activate env_builder
-```
-
 ### Local Installation
 
 Add to your `pubspec.yaml`:
@@ -73,17 +67,20 @@ Generates environment packages from `.env` files:
 env_builder build
 
 # Build with specific environment files
-env_builder build --env-file=.env.dev,.env.prod
+env_builder build --env-file=.env.development,.env.production,.env.staging
 
-# Build with custom output directory
+# Build with custom output directory (default: env)
 env_builder build --output-dir=custom_env
 
+# Skip encryption of sensitive variables
+env_builder build --no-encrypt
+
+# Show detailed output during build process
+env_builder build --verbose
+
 ```
 
 **Planned Features:**
-- `--output-dir`: Custom output directory (default: `packages/env`)
-- `--no-encrypt`: Skip encryption of sensitive variables
-- `--verbose`: Detailed output during build process
 - **Complex Data Types Support**: Handle JSON-like strings (e.g., `APP_CONFIG={"theme":"dark","features":["chat","notifications"]}`)
 - `--config-env-file`: Specify a default configuration file for environment-specific settings
 
@@ -217,7 +214,7 @@ To run the example:
 cd example
 flutter pub get
 # The .env file already exists
-env_builder build --env-file=.env
+env_builder build
 flutter run
 ```
 

bin/env_builder_cli.aot

@@ -39,10 +39,10 @@ class _MyHomePageState extends State<MyHomePage> {
 
   // Just to simulate the use of EnvValue
   void createUser(EnvValue env) {
-    final url = env(Env.createUserUrl);
+    // final url = env(Env.createUserUrl);
     final baseUrl = env(Env.baseUrl);
 
-    print('Response: $baseUrl$url');
+    print('Response: $baseUrl');
   }
 
   @override

example/lib/main.dart

@@ -0,0 +1,58 @@
+# Miscellaneous
+*.class
+*.log
+*.pyc
+*.swp
+.DS_Store
+.atom/
+.buildlog/
+.history
+.svn/
+migrate_working_dir/
+
+# IntelliJ related
+*.iml
+*.ipr
+*.iws
+.idea/
+
+# The .vscode folder contains launch configuration and tasks you configure in
+# VS Code which you may wish to be included in version control, so this line
+# is commented out by default.
+#.vscode/
+
+# Flutter/Dart/Pub related
+# Libraries should not include pubspec.lock, per https://dart.dev/guides/libraries/private-files#pubspeclock.
+/pubspec.lock
+**/doc/api/
+.dart_tool/
+.flutter-plugins-dependencies
+/build/
+/coverage/
+
+# Dart & Flutter
+.dart_tool/
+.packages
+.pub-cache/
+build/
+coverage/
+
+# VS Code
+.vscode/
+
+# IntelliJ / Android Studio
+*.iml
+.idea/
+*.iws
+*.ipr
+*.bak
+
+# Logs and locks
+*.log
+*.lock
+pubspec.lock
+
+# Env files (do not commit secrets)
+.env
+.env.*
+!.env.example

example/packages/custom_env_package/.gitignore

@@ -0,0 +1,10 @@
+# This file tracks properties of this Flutter project.
+# Used by Flutter tool to assess capabilities and perform upgrades etc.
+#
+# This file should be version controlled and should not be manually edited.
+
+version:
+  revision: "adc901062556672b4138e18a4dc62a4be8f4b3c2"
+  channel: "stable"
+
+project_type: package

example/packages/custom_env_package/.metadata

@@ -0,0 +1,3 @@
+## 0.0.1
+
+* TODO: Describe initial release.

example/packages/custom_env_package/CHANGELOG.md

@@ -0,0 +1 @@
+TODO: Add your license here.

example/packages/custom_env_package/LICENSE

@@ -0,0 +1,39 @@
+<!--
+This README describes the package. If you publish this package to pub.dev,
+this README's contents appear on the landing page for your package.
+
+For information about how to write a good package README, see the guide for
+[writing package pages](https://dart.dev/tools/pub/writing-package-pages).
+
+For general information about developing packages, see the Dart guide for
+[creating packages](https://dart.dev/guides/libraries/create-packages)
+and the Flutter guide for
+[developing packages and plugins](https://flutter.dev/to/develop-packages).
+-->
+
+TODO: Put a short description of the package here that helps potential users
+know whether this package might be useful for them.
+
+## Features
+
+TODO: List what your package can do. Maybe include images, gifs, or videos.
+
+## Getting started
+
+TODO: List prerequisites and provide or point to information on how to
+start using the package.
+
+## Usage
+
+TODO: Include short and useful examples for package users. Add longer examples
+to `/example` folder.
+
+```dart
+const like = 'sample';
+```
+
+## Additional information
+
+TODO: Tell users more about the package: where to find more information, how to
+contribute to the package, how to file issues, what response they can expect
+from the package authors, and more.

example/packages/custom_env_package/README.md

@@ -0,0 +1,4 @@
+include: package:flutter_lints/flutter.yaml
+
+# Additional information about this file can be found at
+# https://dart.dev/guides/language/analysis-options