Replies: 2 comments
-
It was a caching issue (?), it seems. Woke up this morning and everything works. I did create another app ( Wow! What a ride. |
Beta Was this translation helpful? Give feedback.
-
When you post to a route like But the data does go somewhere, of course. As per the docs, you can use either the deprecated So if one were to have troubleshooting code that looks like this:
Whichever of those In the above snippet, only would yield all the info. |
Beta Was this translation helpful? Give feedback.
-
This is a bit of a tough one, because the issue could be from one of several packages.
I create a form like so:
When I click the submit button, the rendered output is empty (i.e. the string I typed does not show up; empty string).
NOTE: Elements with a "todos" tag are present on page load, so the form should have a valid target. It looks like this:
I am using
web-inv-route
for routing. Those routes look like:I have been passing around this
req
inherited from theapp
context.The reason for this is that I assumed that I could brute force get my string from the
Wai.Request
. Yet, logging the request after I hit the submit button does not show the input string anywhere in theWai.Request
record. I cannot think of anywhere else it could be.Everything works as expected if I
curl
. It's specifically with the submit button functionality. It should be noted thatweb-inv-route
Request
uses a subset ofWai.Request
. That's part of why I passed in the Wai.Request to the routes. I'm sure there is a more elegant way to handle that, but I want to get things working first.Beta Was this translation helpful? Give feedback.
All reactions