/dev/ stds 5th generation jet fighter abughraib bootstrap Chancellor assignment Chrome apps cloud Dichotomical approach economics framework franchise javascript laptop licencing nerueconomics Oil refinery Postman compatible quantitative easing SFTP competitive advantages shopping smartphonne Term paper Trance music staged shows unix wifi wiki pages

Slim and CI4 working SASS frontend

UI and UX of the web development assigned project is QA most intense if managers aren't tech savvy with development languages and stack. It's nonetheless the developer's fault to provide the coherent and necessary results into the development stack flow, otherwise non WYSIWYG compliant content is apparent and prevalent in progress.

In relation with the recently discussed topics, the HTTP debugging isn’t that easy as it might look like:

http -h http://localhost:4441/form/users/e7c3fdd3-ce8e-4175-a31d-3f7bed0490b1
HTTP/1.1 200 OK
Host: localhost:4441
Date: Tue, 31 Mar 2020 06:07:15 GMT
Connection: close
X-Powered-By: PHP/7.2.29
Accept: application/x-www-form-urlencoded
Accept: text/html
Accept-Encoding: utf8
Content-type: text/html;charset=UTF-8
Access-Control-Allow-Credentials: true
Access-Control-Allow-Origin: 
Access-Control-Allow-Headers: X-Requested-With, Content-Type, Accept, Origin, Authorization
Access-Control-Allow-Methods: GET, POST, PUT, PATCH, DELETE, OPTIONS
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Cache-Control: post-check=0, pre-check=0
Pragma: no-cache

HTML response type header is correct, though I had to correct

HtmlResponseMiddelware.php

        $response = $response->withHeader('Content-type', 'text/html');

explicitly, without debugging info, as suggested, because

HTTP/1.1 200 OK
Host: localhost:4441
Date: Tue, 31 Mar 2020 06:10:51 GMT
Connection: close
X-Powered-By: PHP/7.2.29
Accept: application/x-www-form-urlencoded
Accept: text/html
Accept-Encoding: utf8
Access-Control-Allow-Credentials: true
Access-Control-Allow-Origin:
Access-Control-Allow-Headers: X-Requested-With, Content-Type, Accept, Origin, Authorization
Access-Control-Allow-Methods: GET, POST, PUT, PATCH, DELETE, OPTIONS
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Cache-Control: post-check=0, pre-check=0
Pragma: no-cache
Content-type: text/html; charset=UTF-8

with

HtmlResponseMiddelware.php

        $response = $response->withHeader('Content-type', 'text/plain');

You see, that response in this instance is incorrect, showing the same HTML content type output header, which confuses the debugging, forcing Chrome and Links render HTML text directly.

Anyway, it’s nonetheless the easier part, the heavier issue is _custom.scss layered demand escalation, only allowing it to be user in combination with bootstrap JS imported, CSS ommitting:

import 'bootstrap';

So, working with a set of projects, especially importing enterprise practice development, it has to be an urgency to apply the theme to _custom.scss file, which in turn imports default Bootstrap (frontend framework) styles:

@import "node_modules/bootstrap/scss/bootstrap";

That’s why it’s important to adhere to the standards like ECMA and PSR in business development, be it Golang or PHP web projects. In general, webpack is an awesome dependencies manager and frontend shipper, nothing to complain about. Nevertheless, extensive debugging is needed to assure the delivered content is WYSIWYG compliant and coherent.

%d bloggers like this: