Skip to content
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

Preferably, use preact instead of react #103

Open
Tracked by #72
tu2-atmanand opened this issue Jan 1, 2025 · 0 comments
Open
Tracked by #72

Preferably, use preact instead of react #103

tu2-atmanand opened this issue Jan 1, 2025 · 0 comments
Labels
future idea New Future or improvement, but not urgent, can be implemented in new branch optimization The algo/code can be optimized. A better approach

Comments

@tu2-atmanand
Copy link
Owner

tu2-atmanand commented Jan 1, 2025

  • I think the better idea would be to first find out everything about preact, whether it's a good idea to use it or not. And I might have to first also finish with implementing memo functions in the whole project.
  • Might need to break down my components, like the header and footer of the card will be separate files, etc.
  • Refer Kanban plugin for this and also may be for the above thing.
@tu2-atmanand tu2-atmanand added future idea New Future or improvement, but not urgent, can be implemented in new branch optimization The algo/code can be optimized. A better approach labels Jan 1, 2025
@tu2-atmanand tu2-atmanand moved this to Future Ideas in Task Board Dev Jan 1, 2025
@tu2-atmanand tu2-atmanand changed the title Preferably, use preact instead of react. (Might need to break down my components). Preferably, use preact instead of react Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future idea New Future or improvement, but not urgent, can be implemented in new branch optimization The algo/code can be optimized. A better approach
Projects
Status: Future Ideas
Development

No branches or pull requests

1 participant