Skip to content
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

Remove CodeClass from FilteredData #471

Closed
gogonzo opened this issue Oct 4, 2023 · 11 comments · Fixed by #488 or insightsengineering/teal#964
Closed

Remove CodeClass from FilteredData #471

gogonzo opened this issue Oct 4, 2023 · 11 comments · Fixed by #488 or insightsengineering/teal#964
Assignees
Labels

Comments

@gogonzo
Copy link
Contributor

gogonzo commented Oct 4, 2023

CodeClass will be removed soon, if FilteredData have to keep a code from data loading stage then it should be a character. Consider if code from data loading stage have to be kept in FilteredData.

@chlebowa
Copy link
Contributor

chlebowa commented Oct 6, 2023

If we go with (a) teal_data (b) -> (c) FilteredData (d) -> (e) teal_data (f), I don't see why we wouldn't keep the initial code from (a) in FilteredData. Otherwise you would have to have another entity hold on to it at (c) and modify what comes out of FilteredData at (d).

Store as character, absolutely.

@gogonzo
Copy link
Contributor Author

gogonzo commented Oct 6, 2023

Store as character, absolutely.

Good point. Sounds like setMethod(get_code, "character") will be needed

@chlebowa
Copy link
Contributor

chlebowa commented Oct 6, 2023

Good point. Sounds like setMethod(get_code, "character") will be needed

I'm not sure what you mean.

@gogonzo
Copy link
Contributor Author

gogonzo commented Oct 6, 2023

Code needs to be provided somehow between teal early stages and srv_nested_tabs. FilteredData is the only object which is passed at this moment. If FilteredData will contain code (character) or if code (character) will be passed further we need a method which can subset character code for a specific datasets (because code will contain all datasets code).

Having get_code.character will give us possibility to pass code as character everywhere and extract it when needed.

@chlebowa
Copy link
Contributor

chlebowa commented Oct 6, 2023

Would you not get_code(<teal_data>, names = module$datanames)?

@chlebowa
Copy link
Contributor

chlebowa commented Oct 6, 2023

Thoroughly discussed and clear 👍

@m7pr
Copy link
Contributor

m7pr commented Oct 30, 2023

Hey, this get_code will remain in teal or teal.slice ?
Also, I understand we will remove get_code from teal.data completely? insightsengineering/teal.data#173

@chlebowa
Copy link
Contributor

There is teal.code::get_code and it's not going anywhere. teal.data will inherit this function along with the qenv class, perhaps we will have to re-export it.

@m7pr
Copy link
Contributor

m7pr commented Oct 30, 2023

Just trying to understand which functions we have where. So there will be tea.code::get_code for teal_data and qenv, And teal.data::get_code() is here for TealDatasetConnector, TealDataset and TealDataAbstract. Also teal.data::get_code.default() will be deprecated.

@chlebowa
Copy link
Contributor

All get_code methods currently defined in teal.data will be removed, I believe.

@m7pr
Copy link
Contributor

m7pr commented Oct 30, 2023

Amazing. The less the better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
3 participants