Feature Request: Check for Existing Configuration File
Description
We are planning to add support for a configuration file in this extension. While the presence of this configuration file will not be mandatory for using the extension, it will provide additional details such as:
Groups of files to be converted
Files to be excluded from conversion
Paths for the public and assets folders
This will enhance the accuracy of the conversion process from HTML to Blade templates.
Task
Develop a function to check for the existence of a configuration file in the workspace. The function should:
Verify the presence of a specific configuration file (e.g., config.json).
If the configuration file exists, load and validate its contents.
If the configuration file does not exist, proceed without it but log an informative message to the user.
Acceptance Criteria
The function should accurately detect the presence of the specified configuration file in the workspace.
If the configuration file exists, its contents should be loaded and validated.
If the configuration file does not exist, an informative message should be logged to the user.
Additional Context
This feature will allow for more precise control over the conversion process, improving the overall functionality and user experience of the extension.
Feature Request: Check for Existing Configuration File
Description
We are planning to add support for a configuration file in this extension. While the presence of this configuration file will not be mandatory for using the extension, it will provide additional details such as:
This will enhance the accuracy of the conversion process from HTML to Blade templates.
Task
Develop a function to check for the existence of a configuration file in the workspace. The function should:
config.json).Acceptance Criteria
Additional Context
This feature will allow for more precise control over the conversion process, improving the overall functionality and user experience of the extension.