mep/8: frontend function hints

[dmadisetti]

📝 Summary

@mscolnick this was my very rough draft approach to passing hints upstream:

For reference, this is how observable renders their functions:

and what was suggested:

But I'm sure there's probably a more cohesive marimo style (do we have have any brand docs?):

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
marimo-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 7, 2025 5:40pm
marimo-storybook	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 7, 2025 5:40pm

[akshayka]

No brand docs yet ... but that's a good idea.

At first glance it feels a bit repetitive to include the function signature in the output area? I like the idea of communicating hints and function-ness though ...

[mscolnick]

@dmadisetti is the name configurable on the frontend? is it enforced by the backend?

when happens to the name if it goes from a pure function to non-pure function?

[dmadisetti]

@dmadisetti is the name configurable on the frontend? is it enforced by the backend?

Name will be overwritten as is, which seems reasonable? But the current UI does make it a bit jarring. Might be worth hiding in these cases.

when happens to the name if it goes from a pure function to non-pure function?

Then the TopLevelStatus "hint" indicates that something has gone wrong- but the name is retained. It could be pushed back to "_"

---

Currently unindented comments after (or before) the function are stripped. I'm think we should retain the comments, and have that break "purity" if someone really wanted to intentionally keep it in cell mode.

[dmadisetti]

At first glance it feels a bit repetitive to include the function signature in the output area? I like the idea of communicating hints and function-ness though ...

Agreed. I think this is an issue shared with markdown too. Many possible UIs but one might be using the markdown style blocks of no border, and expansion on click