Conversation
Unit Tests Summary 1 files 33 suites 2m 43s ⏱️ Results for commit 4d2cbdc. ♻️ This comment has been updated with latest results. |
Unit Test Performance DifferenceAdditional test case details
Results for commit 7b71011 ♻️ This comment has been updated with latest results. |
Code Coverage SummaryDiff against mainResults for commit: 4d2cbdc Minimum allowed coverage is ♻️ This comment has been updated with latest results |
averissimo
left a comment
There was a problem hiding this comment.
We should get the namespace of those 2 functions to be teal, maybe change the environment where eval is running for environment(deep_copy_filter), my suggestion or another (better) way
averissimo
left a comment
There was a problem hiding this comment.
Looks good! There's on open comment, that may be moved to a discussion topic
Let's not waste time if it covers problem for now. I just made a small improvement we can improve in the future if somebody touches these lines again |
another PR insightsengineering/teal.slice#675
closes https://github.com/insightsengineering/teal/issues/1683
Problem arises when trying to simplify teal-app creation from independent modules. Let's image following situation, we have a group of templates where each template has data, slices and module functions. Functions for each template are independent and they are not linked with each other. For example slices for template
labs1andlabs2are "independent" set of filters. Sometimes these filters are common filters and they should be shared by the modules - currently teal doesn't provide this, because duplicated filter id-s are raising an error. It makes sense that they will be combined and duplicated ones will be ignored.