atahrijouti / explorer Goto Github PK

As it stands right now, we are using elements that are part of the render to trigger events. The issue that comes up is for example when NavigationBar wants to tell Explorer to render something, it has to do it through dispatching an Event on the appElement.

The issue with this scenario is that Explorer is a child of AppElement, and none might have been mounted from the start. which leads to issue like needing to do export let appElement: HTMLElement | null = null https://github.com/abderrahmane-tj/explorer/blob/master/src/app/index.ts

If we were able to export an observable of some sort instead it would be easier to access without having it null at the start

• Move state to Explorer
• state should contain only nodes in current folder
• go up should reflect URL

• Setup Koa server
• Init routes structure
• hook front-end to back-end
• use PostgreSQL
• GET /root-nodes route
• GET /nodes/:id route
• GET /nodes-from-path/:path(.*) route
• POST /nodes route
• DELETE /nodes/:id route
• PUT /nodes/:id route

• Empty folder
• Folder having children
• Known extensions : txt, image, video, office, pdf...

intex.html still has html in it that is not part of a component.
For total componentization, move that html into typescript

• Implement routes.ts file
• Implement a router system that reflects URL to page element
• Respond to navigation inside node list and push routes to history
• Respond to click on breadcrumb and push routes to history