This document is an attempt to pin down all the things you don't think about when quoting for a project, and hopefully provide a starting point for some kind of framework to make quoting, working and delivering small-medium jobs more predictable and less stressful.
Your task is to create a detailed summary of the conversation so far, paying close attention to the user's explicit requests and your previous actions. This summary should be thorough in capturing technical details, code patterns, and architectural decisions that would be essential for continuing development work without losing context.
Before providing your final summary, wrap your analysis in <analysis> tags to organize your thoughts and ensure you've covered all necessary points. In your analysis process:
- Chronologically analyze each message and section of the conversation. For each section thoroughly identify:
- The user's explicit requests and intents
- Your approach to addressing the user's requests
- Key decisions, technical concepts and code patterns
- Specific details like:
| <script setup lang="ts"> | |
| import StreamingIndicator from '@/components/StreamingIndicator.vue'; | |
| import { useStream } from '@laravel/stream-vue'; | |
| import { onMounted, onUnmounted, ref, watch } from 'vue'; | |
| type Message = { | |
| type: 'response' | 'error' | 'prompt'; | |
| content: string; | |
| }; | |
| const messages = ref<Message[]>([]); | |
| const { data, send, cancel, isStreaming, id } = useStream('chat'); |
This document provides a comprehensive guide to implementing geospatial queries in Laravel applications. It covers setting up your database, installing necessary packages, defining spatial data in your models, and performing various types of geospatial queries using Laravel's Eloquent ORM and query builder.
Table of Contents:
- Introduction to Geospatial Queries in Laravel
- Prerequisites
- Step 1: Setting up Your Database for Spatial Support
- 3.1. PostgreSQL with PostGIS Extension (Recommended)
- 3.2. MySQL (5.6+)
- Step 2: Configuring Laravel Database Connection
| <?php | |
| use Valet\Drivers\ValetDriver; | |
| class LocalValetDriver extends ValetDriver | |
| { | |
| public function serves(string $sitePath, string $siteName, string $uri): bool | |
| { | |
| return true; | |
| } |
| // Remember to install mini-svg-data-uri | |
| // Follow me on twitter for memes @jordienr | |
| import { type Config } from "tailwindcss"; | |
| const { | |
| default: flattenColorPalette, | |
| } = require("tailwindcss/lib/util/flattenColorPalette"); | |
| const svgToDataUri = require("mini-svg-data-uri"); | |
| export default { |
There are two types of markup in Liquid: Output and Tag.
- Output markup (which may resolve to text) is surrounded by
{{ matched pairs of curly brackets (ie, braces) }}- Tag markup (which cannot resolve to text) is surrounded by
| module.exports = { | |
| // forcing the creation of an index.html for every page to allow | |
| // providers serving pages without having to add .html to the url | |
| exportPathMap: async function (defaultPathMap) { | |
| const pathMap = {}; | |
| for (const [path, config] of Object.entries(defaultPathMap)) { | |
| if (path === "/") { | |
| pathMap[path] = config; | |
| } else { |
- Jump down to the plugin
- Try it on Codepen — and heart it!
- Try it on Tailwind Play
- Read my blog post about this plugin - and share it!
and star this gist!
| function PlaceholderImage({ | |
| height, | |
| width, | |
| ...consumerProps | |
| }) { | |
| return ( | |
| <img | |
| {...consumerProps} | |
| alt="" | |
| src={`https://via.placeholder.com/${width}x${height}`} |