| { | |
| "editor.tabSize": 2, | |
| "editor.fontSize": 16, | |
| "editor.formatOnSave": true, | |
| "editor.renderWhitespace": "none", | |
| "editor.renderLineHighlight": "none", | |
| "editor.mouseWheelZoom": true, | |
| "workbench.layoutControl.type": "menu", | |
| "workbench.editor.limit.enabled": true, | |
| "workbench.editor.limit.value": 1, |
| /** @type {import('tailwindcss').Config} */ | |
| export default { | |
| content: ['./resources/**/*.edge', './resources/**/*.{js,ts,jsx,tsx,vue}'], | |
| theme: { | |
| extend: { | |
| fontFamily: { | |
| sans: ['Inter', 'system-ui', 'sans-serif'], | |
| }, | |
| colors: { | |
| primary: '#8E52A9', |
If you are using Rails, Laravel, or AdonisJS (the only one's I know), then these inconsistencies are handled automatically for you.
HTML forms have particular serializing behavior attached to them that you need to understand and address to work with normalized data in your applications.
I see a few talking about it because we stopped using HTML forms with the rise of frontend frameworks. However, they are now returning to HTML forms, so I expect more developers to encounter these surprises.
| openRepo() { | |
| githubDomain="https://github.com/" | |
| remoteUrl="$(git config --get remote.origin.url)" | |
| branch="$(git rev-parse --abbrev-ref HEAD)" | |
| # Replace git protocol with github domain | |
| remoteUrl="${remoteUrl/git\@github\.com\:/$githubDomain}" | |
| # Replace `.git` suffix | |
| remoteUrl="${remoteUrl/.git/}" |
| .markdown { | |
| @apply text-prose font-body text-gray-800; | |
| } | |
| /** | |
| * ------------------------------------------------------ | |
| * Headings | |
| * ------------------------------------------------------ | |
| */ | |
| .markdown h1, .markdown h2, .markdown h3, .markdown h4, .markdown h5 { |
| import Up from './index' | |
| declare module '@ioc:Adonis/Core/HttpContext' { | |
| interface HttpContextContract { | |
| up: Up | |
| } | |
| } |
| // Save inside contracts/validator.ts | |
| declare module '@ioc:Adonis/Core/Validator' { | |
| interface Rules { | |
| disallowEmoji(): Rule | |
| } | |
| } |
I want to spend some time creating a great course on AdonisJS.
I personally DO NOT want to keep it super simple, like a todo app or a blog without any design. I understand that these tutorials does help understand the basics of the framework, but they do not do justice with what you can achieve by using AdonisJS.
Now, I have couple of ideas in mind. Lemme dump them here and use your feedback to make an informed decision.
Creating a little complex end to end application that deals with multiple things at a given point of time. For example: An application that has
| <?xml version="1.0" encoding="UTF-8"?> | |
| <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> | |
| <plist version="1.0"> | |
| <dict> | |
| <key>Ansi 0 Color</key> | |
| <dict> | |
| <key>Color Space</key> | |
| <string>sRGB</string> | |
| <key>Blue Component</key> | |
| <real>0.1803921568627451</real> |
| const actions = {} | |
| describe('Broken suite', () => { | |
| beforeAll(() => { | |
| actions.all = {} | |
| actions.all.before = true | |
| }) | |
| beforeEach(() => { | |
| actions.each1 = {} |
