Nikhil Rao

In the codebase we use "route" and "path" interchangeably. Let's be consistent and stick to "route" since we are based on NextJS routes.

It would be cool if we could run simple code on the client side to avoid network round trips. We can track ideas on how to do this in this...

This can just be a shorthand for ``` pc.input(type_="password") ``` but we can also have nice features like automatically hashing the value before storing it in the state, so we...

See discussion here: https://github.com/pynecone-io/pynecone/discussions/137

We should add components like `pc.div`, `pc.pre`, etc. so users can build more customized components and integrate with libraries like Tailwind.

Currently in order to clear the value of a `pc.input` you need to make it a controlled input (i.e. set the `value` and `on_change` props together). This has the downside...

Expose client token in state

1

Sometimes the event handlers may need to know the specific client that is calling it, to do logic such as rate-limiting. Each client has a token already, so we can...

Sometimes you may want the raw header (for example to get the IP address). We can expose the request object to the event handler. The relevant starting point is here:...

Currently the port can only be set in the `pcconfig.py` file. It would be nice if we could override it during `pc run`.