-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial structure for the second sprint #46
base: master
Are you sure you want to change the base?
Conversation
|
|
c26ee66
to
0553e6c
Compare
I have type errors when I try to extract this declaration
The client is now organized in a clearer structure
ed428fc
to
7d56b97
Compare
But there are still some things to smooth
What we did in this sprint We used reflex to model the users and roles overview and editing pages: doing In the shared and server codeWe implemented the domain logic regarding users, and roles. On the server side, On the clientsideReflex templatingOne of the first obstacle we encountered was the need to convert the html mock I discovered in the meantime that in the templating world, there are solutions We solved all this problems by extending a jsx quasiquoter in such a way that ValidationWe vetted the existing solutions for data validation. Our goals were mainly:
We discovered that the formlets/digestive-functors approach, while very So we created a typeclass based approach which permits the construction of General structure of the applicationOn the clientside, we used a way to structure a large application, which leaves On the smaller end of the scope, we used with great effect the RecursiveDo I felt that the learning curve to understand how to structure an application was Client side routingWe also have been trying to tackle the problem of client-side routing: we are |
Shall I merge or wait for the following?
|
The version of reflex-dom-contrib is the one with the new routing primitives
9e05205
to
0fe7771
Compare
0fe7771
to
ed86de3
Compare
I'm keeping some manually translated code around to use it as an example
Description
The main aim of this sprint is translating a mock roles page and the related role edit page, trying to develop approaches that scale for the problem of how to link back server errors to the part of the ui in which they happened. The scalable solution found for this server-side problem will be then contrasted to the obvious solution for client-side validation, and I'll try to unify the approaches in a single API.
A mock API and server will be constructed, following the architecture of the last sprint, to simulate the behavior of the page.
A particular focus will be put in writing high-level code which expresses complex UI interactions: for example, when the
Product
checkbox is ticked, all the boxes in the submenu should be (and vice-versa).If there's time at the end, contributing back some code to the libraries we're using/fixing haddocks would be a worthwhile accomplishment.
Tech Stack
reflex
,servant
,servant-reflex