iamnamananand996
commented
1 month ago Hi @GabrielePicco,
for part 3
- [ ] rather than hardcoding the template text into code directly, add it into a text file and read it.
I came up of the following solution.
Just, want to check with, if you liked it or not then only will procced with this changes for whole cli application.
Solution
- folder structure
component_template.txt
use bolt_lang::*;
declare_id!("{{PROGRAM_ID}}");
#[component]
#[derive(Default)]
pub struct {{STRUCT_NAME}} {
pub x: i64,
pub y: i64,
pub z: i64,
#[max_len(20)]
pub description: String,
}In the above text file, we need observe the way the variable name are defined. {{PROGRAM_ID}} and {{STRUCT_NAME}}
and do find and replace in the create_component_template_simple function below, before procced this, we need to agree on, either we liked this way for definition or not.
create_component_template_simplefunction
/// Create a component which holds position data.
fn create_component_template_simple(name: &str, program_path: &Path) -> Files {
// Define the path to the template file in the "templates" folder
let template_path = Path::new("templates").join("component_template.txt");
// Read the template content from the text file
let mut template =
fs::read_to_string(&template_path).expect("Failed to read component template file");
let program_id = anchor_cli::rust_template::get_or_create_program_id(name).to_string();
// Replace placeholders with actual values
template = template.replace("{{PROGRAM_ID}}", &program_id);
template = template.replace("{{STRUCT_NAME}}", &name.to_upper_camel_case());
// Return the modified string as part of the function
vec![(program_path.join("src").join("lib.rs"), template)]
}
GabrielePicco
Problem
Right now, if we observe the
cli-applicationit is centralized into 2 big files, which in a long term will become very hard to mange, better to break down these file to specific task files.Solution
lib.rsfilerust_template.rsrather than hardcoding the template text into code directly, add it into a text file and read it.