Nikhil Rao
Nikhil Rao
Currently all state vars must be JSON serializable to send the the frontend. However sometimes it could be useful to have state fields that are only on the backend (i.e....
Currently the first argument to `pc.cond` must be a `pc.Var` with type `bool`. However since JS is lax about converting anything to a bool, perhaps we can relax this requirement...
Currently all state vars need to be defined as fields within the State class. Sometimes it is useful to dynamically add vars after the state class is already defined. Minimally...
Currently Pynecone doesn't detect mutations in list/dict state vars which is annoying and can lead to bugs if one is not careful. Maybe we could create classes `pc.dict` and `pc.list`...
Some event handlers are expected an argument. For example when setting an input, you need ```python class State(pc.State): text: str def change_text(self, text): self.text = text.upper() ``` Then call it...
Currently the example for pc.input is wrong: https://pynecone.io/docs/library/forms/input We call the prop `place_holder` but it should be called `placeholder`
In @Lendemor's work in dynamic vars, we encountered an issue that the default value for the dynamic vars is always `None`. ```python @classmethod def _set_default_value(cls, prop: BaseVar, default_value: Any =...
We can make this part of the core: https://github.com/pynecone-io/pcweb/blob/2c1e3a4813737796155a86c3fe2008f5026f9b77/pcweb/templates/docpage.py#L17
What is this Python project? Pynecone is an open-source, full-stack python framework that makes it easy to build and deploy web apps in minutes. It offers the ease of use...
Currently we only have support for npm components. We should also allow the user to wrap their custom local components.