An ongoing project to catalogue all of these sneaky, hidden, bleeding edge selectors as I prepare my JSConf EU 2012 talk.
Everything is broken up by tag, but within each the selectors aren't particularly ordered.
I have not tested/verified all of these. Have I missed some or got it wrong? Let me know. - A
A friendly reminder that you may need to set this property on your target/selected element to get the styling results you want:
-webkit-appearance:none;
| { | |
| "parser": "babel-eslint", | |
| "env": { | |
| "browser": true, | |
| "jest": true | |
| }, | |
| "plugins": ["react", "jsx-a11y", "import"], | |
| "extends": "airbnb", | |
| "rules": { | |
| "react/jsx-filename-extension": [ |
| root = true | |
| [*] | |
| end_of_line = lf | |
| indent_style = space | |
| indent_size = 2 | |
| charset = utf-8 | |
| trim_trailing_whitespace = true | |
| insert_final_newline = false |
| { | |
| "singleQuote": true, | |
| "trailingComma": "all", | |
| "arrowParens": "avoid" | |
| } |
Ok. I'm going to list off some ideas for projects. You will have to determine if any particular idea is good enough to include in a portfolio. These aren't creative ideas. They likely already exist. Some are way too advanced while others are simplistic.
I will recommend to post any project you make to github and make a github project page for it. Explain in as much detail as possible how you made it, how it can be improved etc. Document it.
If you pick an advanced idea, setup a development roadmap and follow it. This will show some project management skills.
Another piece of advice for those who are design challenged. Use different front end frameworks and use different themes for those frameworks to provide appealing designs without looking like yet another bootstrap site.
| { | |
| "terminal.integrated.fontSize": 14, | |
| "workbench.iconTheme": "material-icon-theme", | |
| "workbench.startupEditor": "newUntitledFile", | |
| "editor.tabSize": 2, | |
| "editor.fontSize": 18, | |
| "editor.lineHeight": 26, | |
| "editor.fontFamily": "Fira Code", |
| function returnpromise(val) { | |
| return new Promise((resolve, reject) => { | |
| if (val > 5) { | |
| resolve("resolved"); // fulfilled | |
| } else { | |
| reject("rejected"); // rejected | |
| } | |
| }); | |
| } |
feat: a new feature
fix: a bug fix
docs: documentation only changes
style: changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
refactor: a code change that neither fixes a bug or adds a feature
perf: a code change that improves performance
chore: changes to the build process or auxiliary tools and libraries such as documentation generation
test: adding missing tests
| ### Keybase proof | |
| I hereby claim: | |
| * I am fegvilela on github. | |
| * I am fernandavilela (https://keybase.io/fernandavilela) on keybase. | |
| * I have a public key ASA8SjIIfYPG8lEBoVHwo1mCWEaNqbznXkUOlvGD91gDjgo | |
| To claim this, I am signing this object: |
