The `macro_f_directory_status_t_initialize_1()` is using `status_value` and `path_value` as the parameters within it but is defining them as `status` and `path`.
Fix this by setting them to `status_value` and `path_value`.
The unit test is improperly initializing them.
How did this test not fail in the past?
It just suddenly started failing.
I'll leave that as a fluke.
It is going that the tests caught it and this fixes it.
.path = f_string_dynamic_t_initialize, \
}
- #define macro_f_directory_status_t_initialize_1(status, path) { \
+ #define macro_f_directory_status_t_initialize_1(status_value, path_value) { \
.status = status_value, \
.path = path_value, \
}
mock_unwrap = 0;
mock_unwrap_f_memory = 0;
- f_directory_status_t data = f_directory_status_t_initialize;
+ f_string_dynamic_t path = macro_f_string_dynamic_t_initialize_1("path", 4, 0);
+ f_directory_status_t data = macro_f_directory_status_t_initialize_1(F_okay, path);
f_directory_status_t data_array[] = { data };
- f_directory_statuss_t datas = { .array = data_array, .used = 1, .size = 1 };
+ f_directory_statuss_t datas = macro_f_directory_statuss_t_initialize_1(data_array, 1, 1);
f_directory_statuss_t datass_array[] = { datas };
{