-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
try to harmonize the templates #496
Conversation
🧪 Code Coverage Summary
Diff against main
Results for commit: 348a473554d3cf185a252f92bca8a0c6e2dd1cb7 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Hi @barnett11 , according to recent experience trying out chevron on -------, I tried to harmonize the templates following #476 . Could you have a look at this? |
if no objections, I will also include https://github.com/insightsengineering/chevron.adr/issues/3 to remove unnecessary variants |
further updated |
the ae tables are updated. I will update read me in #476 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with the philosophy of these changes, but I am a bit concerned about the reaction of the users when their real data lead to an error or an unxepected result. There should be a general strategy to ensure data quality before entering the chevron pipline.
how about we ensure that in basically, we have: loose requirements in strong requirements in |
update half of the templates: from egt01 to vst02_2 --------- Signed-off-by: b_falquet <[email protected]> Co-authored-by: benoit <[email protected]>
correct some typo and documentation Co-authored-by: benoit <[email protected]>
…ineering/chevron into 476_harmonize_templates@main
congratulations on the big merge!!! |
following #476, I tried to make the templates a bit clearer. something added
main
functionsdeco
. titles/footnotes should be handled in citril using loporow_split_var
3. valid_row_path. this checks if a row_path is valid for a table
4. valid_sort_at_path. this conduct the sort based on
row_path
if it is valid. (sort_at_path gives error on incorrect row_path provided, and aet02_1 previously will run into issues if prune_0 = FALSE on empty data)5. get_sort_path. this function will create "" between variables, e.g,
get_sort_path(c("A","B"))
will give "A" "" "B", this is required bysort_at_path
6. tlg_sort_by_var. this functions will sort using "A" and "B", instead of "A" "*" "B". Also will check if the table contains the path. if does not contain the path, the sorting will be ignored.
I think some of the funcitonality should go into tern/rtables. But for now let's use them.
Please review this update in general and I will finalize this PR if no objections. Then everyone can collaborate to harmonize all templates.
@Teninq @BFalquet @duanx9 @crazycatandy @barnett11