kuhlaid / svelte2 Goto Github PK

After some thought I am treating the server-side, that this front-end connects to, as an API for data pushes and pulls. The reason for this is that I want this front-end app to be not be tied to a specific back-end database or service, and certainly did not want it embedded in this code base. So the front-end UI code is completely separate from the back-end code. This will make it easier for others to work with this code for their own purposes.

The next step will be to create a Svelte component for entering information about the back-end API to connect to (to be saved to local storage). The user will enter/copy the API URL into the front-end which would be saved to local storage, so that will be my next step in this development.

Other thoughts -------------------

Work on server side CSRF token generation from a user authenticated session (this session and CSRF token need to be saved on the server to validate data requests from the client); reference https://portswigger.net/web-security/csrf/tokens.

I really debated if the app needed unique URLs for each component/page (since these could sort of be routed using server requests to specify the component). I felt the Every framework handled this well, but I couldn't justify it in Svelte. Since this will be used as a non-public app, unique URLs do not seem important or useful so I will not bother with routing to more than one URL to deliver content.

While some files are being cached by the service worker, some are being cached to disk. Looking into reason for this.

One of the problems I am having is understanding how Svelte processes Promises when a component is loaded (either initially or subsequently). I was working specifically with the Articles.svelte component but could not find a way to pull the values of a Promise into a text field from bound data store. What I was seeing was '[object Promise]' in the place of the Promise value but when writing to the console I see that a value is resolved in the Promise. I understanding of Svelte or Promises seems to be lacking in this area but I can't tell where the issue lies.

Comment like this https://github.com/kuhlaid/svelte2/blob/master/src/ApiSettingsIdb.svelte#L1
made debugging very hard. It's much easier if you move that as JS comment.

<script>
/* 
    @abstract This component will be used to update the URL of the server-side API to connect to.
    We need to read the localstorage strApiUrl value and copy to a writable variable.

    @todo Check the session token with the API server.
    Check if the user has an active session with a back-end API and save session.
*/ 
...
</script>

Most of my cache issues come from the Workbox precache 'injectManifest' that happens with the service worker. What I need to happen is copy the src files to a 'staging area' where I can replace the 'cache' constants in the scripts BEFORE the Workbox precache is executed and the run the build rollup off of the staging files. This 'should' cause Workbox to treat the files as updated since the files will be actually updating and thus assign them different revision numbers from the new file hashes.