-
Notifications
You must be signed in to change notification settings - Fork 757
Document AppMeta and make it public
#6939
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
docs/api/app.md
Outdated
|
|
||
| ::: marimo.app_meta | ||
|
|
||
| ::: marimo._runtime.app_meta.AppMeta |
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.
we don't normally document private classes, but since this is the return type of a public function, we should likely make this class public as well
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.
|
@akshayka I want to make this public before merging. As @mscolnick points out, it's ugly to document something from a hidden module. |
|
@mscolnick much better now, assuming we're cool with making it public like this.
|
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.
looks good, thanks!
|
you will need to run |
|
@mscolnick should be all good now. |


This PR was made apon reflecting this message on Discord.
The user in this case was trying to figure out whether or not there was a present mode whenever you access the app meta information. The documentation doesn't actually confirm if this is the case. It doesn't list all the values that the run mode can represent.
Hence, I figured adding the
AppMetaclass to our documentation. That way a user could at least confirm themselves if it is/not supported.