Seperation of backend and frontend

[Hamza-Azeem]

Hello,

I wanted to know the possibility of migrating the frontend logic to a seperate framework or library like angular or react?
I find that the logic of frontend is tightly coupled with backend and it often takes alot of time from me to debug or fix code in frontend which in my opinion should be simpler to do.
What do you think @jesperpedersen ?

[jesperpedersen]

Yeah, we can go to React - it seems the most used of the two.

Feel free to highlight the benefits it will bring

[jesperpedersen]

What is Auth ? Do you mean the Keycloak issue ?

[7amok4a]

@jesperpedersen

What is Auth ? Do you mean the Keycloak issue ?

I mean the login page

[jesperpedersen]

Yes, that is a good starting point

[7amok4a]

@jesperpedersen
Great. Should I create a separate branch in my fork for the frontend work, right?

[jesperpedersen]

@7amok4a Yes, I'm a bit busy this week so the UI should be relative stable - can't promise though. Announce the branch once you have something working, then merge other peoples work and submit as one. Put all names in the commit message

[jesperpedersen]

@Hamza-Azeem Did you look at Typescript ?

[Hamza-Azeem]

@jesperpedersen Sorry for the late reply, I am more of a JS guy but I don't mind picking up TS along the way.
The thing is, I don't know how to exactly start this, as it will require a new project for the frontend, and also refactoring a lot of the backend to send consistent APIs to the new frontend. Do you have any ideas or places to begin with?

[jesperpedersen]

@Hamza-Azeem It requires a public work branch in your fork that people can contribute to. Once you have the foundation working then you announce the work branch here.

Its a work branch so it doesn't even have to work - yet alone compile.