Open npaszty opened 7 months ago
That's not quite enough information, @npaszty. What version of tmc are you using? Your sessionInfo
suggests a vanilla session.
Can you provide the application code?
of course. apologies. here is some context too.
we are moving apps off BEE and onto Apollo or OCEAN depending on the need. This specific app we are testing locally on Apollo. The app works but just sharing the issue per console instructions.
we are also moving away from manually managing custom libraries to initializing renv
Here is the top of the renv.lock file.
"R": {
"Version": "4.2.2",
"Repositories": [
{
"Name": "NEST_latest",
"URL": "https://packages.roche.com/Non-Validated/latest"
},
{
"Name": "CRANMirror",
"URL": "https://packages.roche.com/CRAN/latest"
},
{
"Name": "RSPM",
"URL": "https://packages.roche.com/CRAN/latest"
}
]
},
The list of teal* packages from the packages tab. Note that we are using teal.data 0.3.0 instead of 0.4.0
If you really would like to see the app.R then I can share that but it's quite long and we've been running it for years without issue so this issue is just cropping up because of the move to Apollo and using different versions of the teal packages.
All right.
We are in the midle of releasing core teal
packages to CRAN. teal.data
was just published, actually :champagne: :partying_face: teal.slice
and teal
will soon follow (this coming February).
Your app code should be updated to accommodate a major refactor. You can get some migration pointers here and in vignettes. If you are using your won modules, have a look here.
Let me know if this helps or whether you need more information.
thanks @chlebowa
address errors as they arise but for now was just reporting the issue given instruction in console. thanks for the references and the heads up about the coming refactoring. will open an issue in our repo to keep on the radar especially since we have other apps for which we built mostly custom modules still using the teal framework though.
OK then. If you find you can't afford to properly rebuild modules, you can use teal::as_tdata
as a temporary measure.
not sure what you mean by properly rebuild modules. we aren't building modules just using out of the box TMC like tm_variable_browser(), tm_data_table() and tm_t_summary().
we built mostly custom modules
Sorry if I misunderstood.
we have other apps where we have a lot of custom modules but the one that is being migrated and triggered this note to console is using TMC out of the box.
Now I get it :+1:
@npaszty, we have completed the release of all teal
frameworks and modules to adhere to our latest teal
version. Could you please try installing all the packages again?
There will be breaking changes, and here is the guide to migrate your app.
Since your app uses tmc out of the box, you probably only need to update your data
argument in teal::init
.
What happened?
sessionInfo()
Relevant log output
No response
Code of Conduct
Contribution Guidelines
Security Policy