[dx] Allow vscode to search inside md files by default (#3105)
Before this PR all .md files were targeted by the `.ignore` file, which has bitten me on a number of occasions since .md files often contain valuable information (e.g. the vscode extensions docs). This PR unignores .md files while still ignoring _generated_ .md files like our changelogs, the api-report files, and the generated docs sections. Additionally, the `yarn format` and `yarn lint` commands were configured slightly differently, which was confusing, so I've unified those and simplified the lint.ts script at the same time. ### Change Type - [ ] `patch` — Bug fix - [ ] `minor` — New feature - [ ] `major` — Breaking change - [ ] `dependencies` — Changes to package dependencies[^1] - [ ] `documentation` — Changes to the documentation only[^2] - [ ] `tests` — Changes to any test code only[^2] - [x] `internal` — Any other changes that don't affect the published package[^2] - [ ] I don't know [^1]: publishes a `patch` release, for devDependencies use `internal` [^2]: will not publish a new version
This commit is contained in:
parent
e527d7d0d7
commit
47a85896e0
21 changed files with 78 additions and 123 deletions
|
@ -59,7 +59,6 @@ Note that `onUiEvent` is only called when interacting with the user interface. I
|
|||
|
||||
See the [tldraw repository](https://github.com/tldraw/tldraw/tree/main/apps/examples) for an example of how to customize tldraw's user interface.
|
||||
|
||||
|
||||
## Overrides
|
||||
|
||||
The content of tldraw's menus can be controlled via the `overrides` prop. This prop accepts a [TLUiOverrides](/reference/tldraw/TLUiOverrides) object, which has methods for each part of the user interface, such as the `toolbar` or `keyboardShortcutsMenu`.
|
||||
|
|
|
@ -10,7 +10,7 @@ order: 0
|
|||
|
||||
You can use the tldraw SDK to craft infinite canvas experiences for the web. It's perfect for collaborative whiteboards but you can use it for lots of other things, too.
|
||||
|
||||
By the end of this guide you will have made something that looks like this:
|
||||
By the end of this guide you will have made something that looks like this:
|
||||
|
||||
<Embed className="article__embed--quickstart" src="https://examples.tldraw.com/develop" />
|
||||
|
||||
|
@ -50,26 +50,26 @@ To render the Tldraw component
|
|||
This will render a full screen canvas:
|
||||
|
||||
```javascript
|
||||
import { Tldraw } from "tldraw";
|
||||
import "./index.css";
|
||||
import { Tldraw } from 'tldraw'
|
||||
import './index.css'
|
||||
|
||||
export default function App() {
|
||||
return (
|
||||
<div style={{ position: 'fixed', inset: 0 }}>
|
||||
<Tldraw />
|
||||
</div>
|
||||
);
|
||||
return (
|
||||
<div style={{ position: 'fixed', inset: 0 }}>
|
||||
<Tldraw />
|
||||
</div>
|
||||
)
|
||||
}
|
||||
```
|
||||
|
||||
## Next Steps
|
||||
|
||||
Now that you have your canvas working, you may be wondering: what next?
|
||||
Now that you have your canvas working, you may be wondering: what next?
|
||||
|
||||
You can try:
|
||||
You can try:
|
||||
|
||||
- Giving the editor a makeover by [customizing the UI](/docs/user-interface)
|
||||
- Adding your own [shapes](/docs/shapes) and [tools](/docs/tools)
|
||||
- Providing collaboration using [multiplayer](https://github.com/tldraw/tldraw-yjs-example)
|
||||
- Providing collaboration using [multiplayer](https://github.com/tldraw/tldraw-yjs-example)
|
||||
|
||||
We provide the above examples and more in our [examples section](/examples). Go build something creative and please do share it with us in our [#show-and-tell](https://discord.com/invite/SBBEVCA4PG) channel on Discord!
|
||||
|
|
|
@ -60,21 +60,24 @@ You need to have a psql client [installed](https://www.timescale.com/blog/how-to
|
|||
|
||||
## Sending emails
|
||||
|
||||
We are using [Resend](https://resend.com/) for sending emails. It allows us to write emails as React components. Emails live in a separate app `apps/tl-emails`.
|
||||
We are using [Resend](https://resend.com/) for sending emails. It allows us to write emails as React components. Emails live in a separate app `apps/tl-emails`.
|
||||
|
||||
Right now we are only using Resend via Supabase, but in the future we will probably also include Resend in our application and send emails directly.
|
||||
|
||||
The development workflow is as follows:
|
||||
|
||||
### 1. Creating / updating an email template
|
||||
To start the development server for email run `yarn dev-email` from the root folder of our repo. You can then open [http://localhost:3333](http://localhost:3333) to see the result. This allows for quick local development of email templates.
|
||||
|
||||
To start the development server for email run `yarn dev-email` from the root folder of our repo. You can then open [http://localhost:3333](http://localhost:3333) to see the result. This allows for quick local development of email templates.
|
||||
|
||||
Any images you want to use in the email should be uploaded to supabase to the `email` bucket.
|
||||
|
||||
Supabase provides some custom params (like the magic link url) that we can insert into our email, [check their website](https://supabase.com/dashboard/project/faafybhoymfftncjttyq/auth/templates) for more info.
|
||||
|
||||
### 2. Generating the `html` version of the email
|
||||
Once you are happy with the email template you can run `yarn build-email` from the root folder of our repo. This will generate the `html` version of the email and place it in `apps/tl-emails/out` folder.
|
||||
|
||||
Once you are happy with the email template you can run `yarn build-email` from the root folder of our repo. This will generate the `html` version of the email and place it in `apps/tl-emails/out` folder.
|
||||
|
||||
### 3. Updating the template in Supabase
|
||||
|
||||
Once you have the `html` version of the email you can copy it into the Supabase template editor. You can find the templates [here](https://supabase.com/dashboard/project/faafybhoymfftncjttyq/auth/templates).
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
<!DOCTYPE html>
|
||||
<!doctype html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8" />
|
||||
|
@ -46,5 +46,4 @@
|
|||
<script type="module" src="./src/main.tsx"></script>
|
||||
<noscript>You need to enable JavaScript to run tldraw. ✌️</noscript>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
|
|
@ -5,8 +5,6 @@ category: basic
|
|||
priority: 1
|
||||
---
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
The `Tldraw` component provides the tldraw editor as a regular React component. You can put this component anywhere in your React project. In this example, we make the component take up the height and width of the container.
|
||||
|
|
|
@ -5,8 +5,6 @@ category: basic
|
|||
priority: 5
|
||||
---
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
When the `Tldraw` component's `inferDarkMode` is true, the editor will infer its initial theme based on the user's system preferences, if available. You can toggle the dark mode by pressing `Command + /`.
|
||||
|
|
|
@ -5,8 +5,6 @@ category: basic
|
|||
priority: 2
|
||||
---
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
If the `persistenceKey` prop is provided to the `<Tldraw/>` component, the editor will persist its data locally under that key.
|
||||
|
|
|
@ -1,5 +1,4 @@
|
|||
/* Resize handles are normally on top, but We're going to give shape handles priority */
|
||||
.tl-user-handles {
|
||||
z-index: 101;
|
||||
|
||||
}
|
||||
}
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
<!DOCTYPE html>
|
||||
<!doctype html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="UTF-8" />
|
||||
|
|
|
@ -1,3 +1,3 @@
|
|||
# Health Worker
|
||||
|
||||
Accepts webhooks from [Updown](https://updown.io/), sends them to our Discord.
|
||||
Accepts webhooks from [Updown](https://updown.io/), sends them to our Discord.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue