Idea or thought behind technical implementation is divide big problem to multiple small problems. Small problems are nothing but basic components implemented in project. Application will lose its state on reloading.
Checkout this video
demo.webm
I have used React 17 to develop this requirement.
Basic components will solve very small problems or basic problems in application. Such as input value, or a content editable div as input. These components when used along will create multiple views to interact with each other.
This implementation is implemented by thinking in perspective of react. But I always wonder if I could build framework-less components. Then could write Bridges, Abstractions around frameworks for components that are framework-less.
Comment list component implemented needs to be implemented using basic component. but due to time crunch it is implemented without basic component but breaking into small components.
Most of things are still remaining. I have added comments in few component as of now with first commit.
To implement basic components. Why? problems are small
Exact calculation of placement of icon in editor it is still buggy but can be solved in next iteration. To think if should I go with canvas or layer implementation for editor. But extension in futures might need canvas for few use cases.
As said build framework-less components and make it open source.
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.