Consider moving Rest Mock's frontend to framework #182

New Issue

bema · 2023-05-11T10:52:52+02:00

bema commented

2023-05-11 10:52:52 +02:00

We need to consider pros and cons of moving frontend of REST Mock to some frameworks. Current solution is too time consuming to maintain.

Points to consider:

Which framework?
Moving to framework vs. cleaning up codebase

We need to consider pros and cons of moving frontend of REST Mock to some frameworks. Current solution is too time consuming to maintain. Points to consider: 1. Which framework? 2. Moving to framework vs. cleaning up codebase

bema added this to the Release 11.4 milestone 2023-05-11 10:52:52 +02:00

bema added the

Spike

label 2023-05-11 10:52:52 +02:00

widlam commented

2023-05-11 13:06:21 +02:00

REST Mock need some frameworks. In my opinion we need to consider them by what are the most repeating tasks for frontend.

Looking at the frontend tasks, the most it's about improving responsiveness, so primarily let's think about TailwindCSS(framework that make us instead of writing dozens of CSS classes and properties write class for HTML tag for example instead of writing "text-align: center;" in CSS file, we add for HTML tag class text-center, and if that property needs an unit the tailwind chooses the most responsive option.)
In many situations, we have to add new functions, or expanding existing. That in vanilla solutions often require writing a lot of code that currently exist. Due to that problem I propose to consider some component based framework like or if we want app to works fast, and need to take less time to implement changes .

Cleaning up codebase it's good solution for other WebTools, but for REST Mock if we're going to adding new features, sooner or later that move should be done. The more functions we'll need to rewrite, the longer it will take. So fourth milestone after fixing some backend problem in that tool will be the best time to first move frontend from backend, and second move to some framework.

REST Mock need some frameworks. In my opinion we need to consider them by what are the most repeating tasks for frontend. 1. - [ ] Looking at the frontend tasks, the most it's about improving responsiveness, so primarily let's think about TailwindCSS(framework that make us instead of writing dozens of CSS classes and properties write class for HTML tag for example instead of writing "text-align: center;" in CSS file, we add for HTML tag class text-center, and if that property needs an unit the tailwind chooses the most responsive option.) ![tailwindCSS](https://tailwindcss.com/docs/installation) - [ ] In many situations, we have to add new functions, or expanding existing. That in vanilla solutions often require writing a lot of code that currently exist. Due to that problem I propose to consider some component based framework like ![Vue.js](https://vuejs.org/guide/introduction.html) or if we want app to works fast, and need to take less time to implement changes ![Next.js](https://nextjs.org/docs). 2. Cleaning up codebase it's good solution for other WebTools, but for REST Mock if we're going to adding new features, sooner or later that move should be done. The more functions we'll need to rewrite, the longer it will take. So fourth milestone after fixing some backend problem in that tool will be the best time to first move frontend from backend, and second move to some framework.

bema commented

2023-10-23 11:48:39 +02:00

I and @widlam decided to rewrite whole frontend using Vue.js.

bema closed this issue

2023-10-23 11:48:39 +02:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: R11/release11-tools#182