GitXplorerGitXplorer
g

optimal-stack

public
0 stars
1 forks
0 issues

Commits

List of commits on branch main.
Verified
985eb1436f9af1a2f6fb3bb646ec72aadf602ec2

Update README.md

ggurdiga committed 4 years ago
Unverified
e2349e9f90b0a9b2a30716298690f4402bda5feb

Housekeeping

ggurdiga committed 4 years ago
Unverified
ac7cc82f943dd7692bc59f7182040051d360fe37

Extract AppHTMLElement

ggurdiga committed 4 years ago
Unverified
112d91d3d770b83f258ca93a63c8b1cb8286784f

app-layout: the unit test passes

ggurdiga committed 4 years ago
Unverified
bf5933e1e3d7e75be4e4d64cbd24e0526c273d35

app-layout: a failing unit test

ggurdiga committed 4 years ago
Unverified
6eb680fe93d3d71940f609591ab657968d128e2b

global.css: add color-scheme: dark light;

ggurdiga committed 4 years ago

README

The README file for this repository.

Optimal Stack™

Here I’m playing with the idea of having the simplest working frontend stack:

  • No transpilation;
  • Web Components handle the abstraction;
  • Type-checking is done with TypeScript (see jsconfig.json);
  • Generally the workflow is optimised for VSCode.

Web Components Guidelines

  • The component class + its template as a separate HTML file;
  • The component loads its subcomponents with a <script> tag in its template.

TODO

  • Add HTML linting? (tidy sucks?!)
  • Add linting for other things?
  • Figure out the unit testing.