jonasbuntinx / purescript-react-realworld Goto Github PK

We should create a hosted demo for inclusion in the 2021 Frontend Framework Comparison. (2020 post).

@wryk, would you like to help with this too while you're tackling thomashoneyman/purescript-halogen-realworld#21 ?

Sorry for bothering you with another possibly naive question but from the code review I'm not able to grasp the idea how important is the initialization of the routing signal.
I mean currently (even on the branch) the routing signal is initialized with Home value but it seems that this doesn't really impact the app behavior - it displays correct content for an initial url.
Could you please give me a hint how is it possible that initial app routing works correctly with this predefined constant Home route and why we don't have to parse the url during signal initialization?

What do you think about using lookupEnv and adding purescript-dotenv dependency to this project so we can have a bit more elegant (no direct FFI) way of handling configuration? Is it worth it? Should I provide a PR?

Hi,

I'm learning a lot by reading your example application :-) Thanks a lot for building it!

I'm not sure if this is a real issue but I can imagine that when I want to render some pieces of the app on the server the unsafePerformEffect from Conduit.Env.Routing which triggers some DOM related actions could possibly cause a problem. Probably on the server we want to use "mock" of the PushStateInterface or something to render the initial JSX. What do you think?

Do you think that it is feasible to move navigate and redirect to the current environment so we end up with has something like this:

type Env = { ..., routing :: { signal :: RoutingSignal, navigate :: ..., redirect :: ... }}

Hey, thank you for putting this together, this is answering a ton of questions I have on how to structure things, especially the AppM.

One thing I'm struggling with is how to use the useHalo hook? And more generally, how could I convert one of the more complex examples, such as a Page, into a component only using hooks?

Thank you in advance, sorry is this is the wrong forum to ask!

Hello!

Due to governance changes, we are now using the realworld.io domain for the RealWorld demo (both client and API).
Requests from conduit.productionready.io are redirected to api.realworld.io, but such a redirection might lead to inconsistent responses.

We encourage domain change for the community.
If this repository is maintained anymore, we'll consider hosting a demo of your implementation in a few weeks with the domain change.

The demo link will be added to the RealWorld documentation.

Currently errors in Conduit.Data.Jwt are silently ignored because toAuth uses hush and errors in Lefts are dropped to Nothing.

When for example Webgear Realworld is used for a server, the following token error is reported:

JSONDecodeError: (Named "Jwt" (AtKey "username" MissingValue))

(Because apparently the Webgear Realworld implementation at the server does not encode username and exp in the login response. Things like these are hard to find without console logging of token errors.)

In maridonkers/purescript-react-realworld branch tokenlogging there's console logging added. Will do a pull request for this.