Merge pull request #9933 from stavares843/master

chore(typos): fix typos
This commit is contained in:
dng authored and GitHub committed 2022-10-28 13:43:50 -07:00
commit 35bb20ba63
23 files changed
+38 -38

No files matched your search

+1 -1
View File
@@ -183,7 +183,7 @@ Then edit and visit any of the following sites:
Site | Directory | Description | Local development server
---- | --------- | ----------- | ------------------------
[supabase.com](https://supabase.com) | `/apps/www` | The main website | http://localhost:3000
[supabase.com/docs](https://supabase.com/docs) | `apps/reference` | Guides and Reference documentaion | http://localhost:3010/docs
[supabase.com/docs](https://supabase.com/docs) | `apps/reference` | Guides and Reference documentation | http://localhost:3010/docs
[POC] Community forum | `/apps/temp-community-forum` | GitHub Discussions in a Next.js site | http://localhost:3002
[POC] DEV articles site | `/apps/temp-community-tutorials` | A Next.js site for our DEV articles (which community members can write) | http://localhost:3003
+1 -1
View File
@@ -15,7 +15,7 @@ import Process from '@site/docs/careers/_snippets/process.mdx'
We're looking for Graphic / Web Designers to join our team to help change the way developers build their applications.
You'll be primarily responsible for growing our marketing and brand collataral across the entire Supabase ecosystem.
You'll be primarily responsible for growing our marketing and brand collateral across the entire Supabase ecosystem.
You'll be an indispensable part of team, by working very closely with our sales, marketing, front end team, founders and backend engineers; you'll be directly contributing to brand decisions, building a team culture and co authoring internal processes for a growing team. We want to expand our marketing efforts rapidly throughout 2022 and want you to be at the centre of growing and nurturing our brand, while also nurturing new talent that come on board.
+1 -1
View File
@@ -690,7 +690,7 @@ div[class*=' codeBlockTitle'] {
font-size: 0.8rem !important;
border-color: #444;
}
.repsonse-header {
.response-header {
border-radius: 0 0 4px 4px;
}
+2 -2
View File
@@ -149,7 +149,7 @@ supabaseClient
.subscribe()
```
We will deprecate the `.from().on().subscribe()` method previosuly used for listening to postgres changes.
We will deprecate the `.from().on().subscribe()` method previously used for listening to postgres changes.
### Deprecated setAuth()
@@ -171,7 +171,7 @@ Deprecated and removed `setAuth()` . To set a custom `access_token` jwt instead,
- `gotrue-js`
- `supabase-js` client allows passing a `storageKey` param which will allow the user to set the key used in local storage for storing the session. By default, this will be namespace-d with the supabase project ref. ([PR](https://github.com/supabase/supabase-js/pull/460))
- `signIn` method is now split into `signInWithPassword` , `signInWithOtp` , `signInWithOAuth` ([PR](https://github.com/supabase/gotrue-js/pull/304))
- Deprecated and removed `session()` , `user()` in favour of using `getSession()` instead. `getSession()` will always return a valid session if a user is already logged in, meaning no more random logouts. ([PR](https://github.com/supabase/gotrue-js/pull/299))
- Deprecated and removed `session()` , `user()` in favor of using `getSession()` instead. `getSession()` will always return a valid session if a user is already logged in, meaning no more random logouts. ([PR](https://github.com/supabase/gotrue-js/pull/299))
- Deprecated and removed setting for `multitab` support because `getSession()` and gotrue’s reuse interval setting takes care of session management across multiple tabs ([PR](https://github.com/supabase/gotrue-js/pull/366))
- No more throwing of random errors, gotrue-js v2 always returns a custom error type: ([PR](https://github.com/supabase/gotrue-js/pull/341))
- `AuthSessionMissingError`
+1 -1
View File
@@ -127,7 +127,7 @@ Globally distributed TypeScript functions to execute custom business logic. [Doc
<br />
## Project Managment
## Project Management
### CLI
@@ -47,7 +47,7 @@ You can also assign roles to your team members with different access levels. The
| **Members** |
| Add an Owner | ✅ | | |
| Remove an Owner | ✅ | | |
| Add an Adminstrator | ✅ | ✅ | |
| Add an Administrator | ✅ | ✅ | |
| Remove an Administrator | ✅ | ✅ | |
| Add a Developer | ✅ | ✅ | |
| Remove a Developer | ✅ | ✅ | |
@@ -49,7 +49,7 @@ Click `Save` to create the new table.
## Step 3: Setup your Next.js App with SuperTokens.
Since the scope of this guide is limited to the intergration between SuperTokens and Supabase, you can refer to the SuperTokens website to see [how to setup your Next.js app with SuperTokens](https://supertokens.com/docs/thirdpartyemailpassword/nextjs/about).
Since the scope of this guide is limited to the integration between SuperTokens and Supabase, you can refer to the SuperTokens website to see [how to setup your Next.js app with SuperTokens](https://supertokens.com/docs/thirdpartyemailpassword/nextjs/about).
Once you finish setting up your app, you will be greeted with the following screen
+1 -1
View File
@@ -770,6 +770,6 @@ At this stage you have a fully functional application!
- Explore the [pre-built Auth UI for React](https://supabase.com/docs/guides/auth/auth-helpers/auth-ui).
- Explore the [Auth Helpers for Next.js](https://supabase.com/docs/guides/auth/auth-helpers/nextjs).
- Explore the [Supabase Cache Helpers](https://github.com/psteinroe/supabase-cache-helpers).
- See the [Next.js Supscription Payments Starter](https://github.com/vercel/nextjs-subscription-payments) template on GitHub.
- See the [Next.js Subscription Payments Starter](https://github.com/vercel/nextjs-subscription-payments) template on GitHub.
- Got a question? [Ask here](https://github.com/supabase/supabase/discussions).
- Sign in: [app.supabase.com](https://app.supabase.com)
@@ -31,7 +31,7 @@ export default function CustomCodeBlock({
</div>
{response && (
<>
<div className={'code-with-header repsonse-header'}>
<div className={'code-with-header response-header'}>
<a
className="code-header has-hover-pointer"
style={
+1 -1
View File
@@ -26,7 +26,7 @@ Global variables can be overridden at root like this:
}
```
Styles can be overriden like this:
Styles can be overridden like this:
```css
#__docusaurus {
+2 -2
View File
@@ -147,7 +147,7 @@ supabaseClient
.subscribe()
```
We will deprecate the `.from().on().subscribe()` method previosuly used for listening to postgres changes.
We will deprecate the `.from().on().subscribe()` method previously used for listening to postgres changes.
### Deprecated setAuth()
@@ -169,7 +169,7 @@ Deprecated and removed `setAuth()` . To set a custom `access_token` jwt instead,
- `gotrue-js`
- `supabase-js` client allows passing a `storageKey` param which will allow the user to set the key used in local storage for storing the session. By default, this will be namespace-d with the supabase project ref. ([PR](https://github.com/supabase/supabase-js/pull/460))
- `signIn` method is now split into `signInWithPassword` , `signInWithOtp` , `signInWithOAuth` ([PR](https://github.com/supabase/gotrue-js/pull/304))
- Deprecated and removed `session()` , `user()` in favour of using `getSession()` instead. `getSession()` will always return a valid session if a user is already logged in, meaning no more random logouts. ([PR](https://github.com/supabase/gotrue-js/pull/299))
- Deprecated and removed `session()` , `user()` in favor of using `getSession()` instead. `getSession()` will always return a valid session if a user is already logged in, meaning no more random logouts. ([PR](https://github.com/supabase/gotrue-js/pull/299))
- Deprecated and removed setting for `multitab` support because `getSession()` and gotrue’s reuse interval setting takes care of session management across multiple tabs ([PR](https://github.com/supabase/gotrue-js/pull/366))
- No more throwing of random errors, gotrue-js v2 always returns a custom error type: ([PR](https://github.com/supabase/gotrue-js/pull/341))
- `AuthSessionMissingError`
@@ -49,7 +49,7 @@ Click `Save` to create the new table.
## Step 3: Setup your Next.js App with SuperTokens.
Since the scope of this guide is limited to the intergration between SuperTokens and Supabase, you can refer to the SuperTokens website to see [how to setup your Next.js app with SuperTokens](https://supertokens.com/docs/thirdpartyemailpassword/nextjs/about).
Since the scope of this guide is limited to the integration between SuperTokens and Supabase, you can refer to the SuperTokens website to see [how to setup your Next.js app with SuperTokens](https://supertokens.com/docs/thirdpartyemailpassword/nextjs/about).
Once you finish setting up your app, you will be greeted with the following screen
+1 -1
View File
@@ -771,6 +771,6 @@ At this stage you have a fully functional application!
- Explore the [pre-built Auth UI for React](https://supabase.com/docs/guides/auth/auth-helpers/auth-ui).
- Explore the [Auth Helpers for Next.js](https://supabase.com/docs/guides/auth/auth-helpers/nextjs).
- Explore the [Supabase Cache Helpers](https://github.com/psteinroe/supabase-cache-helpers).
- See the [Next.js Supscription Payments Starter](https://github.com/vercel/nextjs-subscription-payments) template on GitHub.
- See the [Next.js Subscription Payments Starter](https://github.com/vercel/nextjs-subscription-payments) template on GitHub.
- Got a question? [Ask here](https://github.com/supabase/supabase/discussions).
- Sign in: [app.supabase.com](https://app.supabase.com)
+1 -1
View File
@@ -50,7 +50,7 @@ After testing this for a while we're very happy with this pattern. Errors are ha
Our goal for `supabase-js` is to tie together many sub-libraries. Each sub-library is a standalone implementation for a single external system. This is one of the ways we support existing open source tools.
To maintain this philosophy, we created [`gotrue-js`](https://github.com/supabase/gotrue-js), a library for Netlify's GoTrue auth server. This libary includes a number of new additions, including third-party logins.
To maintain this philosophy, we created [`gotrue-js`](https://github.com/supabase/gotrue-js), a library for Netlify's GoTrue auth server. This library includes a number of new additions, including third-party logins.
Previously:
@@ -45,7 +45,7 @@ there are no updates to PostgreSQL in between releases, the patch version will b
The recent wave of Graviton 2 instances from AWS introduces support for the Large System Extensions (LSE). This looks to greatly enhance
application performance through atomics, and
[improves locking and synchronisation performance across large systems](https://github.com/aws/aws-graviton-getting-started#building-for-graviton-and-graviton2).
[improves locking and synchronization performance across large systems](https://github.com/aws/aws-graviton-getting-started#building-for-graviton-and-graviton2).
### Preliminary Benchmarks
@@ -536,11 +536,11 @@ Average is coming in at `2.50ms` which is 16% slower than simple-hstore and 21%
We'll just draw [the rest of the owl][kym-rest-of-owl] now.
What's [HyperLogLog][wiki-hll] you ask? Well it's just a probablistic data structure! Don't worry if you've never heard of it before, it's a reasonably advanced concept.
What's [HyperLogLog][wiki-hll] you ask? Well it's just a probabilistic data structure! Don't worry if you've never heard of it before, it's a reasonably advanced concept.
You may have heard of [Bloom Filters][wiki-bloom-filter] and they're _somewhat_ related but they're not quite a great fit for the problem we're solving since we want to know how many people have seen a particular post. Knowing whether one user has seen a particular post is useful too -- but not quite what we're solving for here (and we'd have to double-check our false positives anyway if we wanted to be absolutely sure).
HyperLogLog provides a probablistic data structure that is good at counting _distinct_ entries, so that means that the count _will not_ be exact, but be reasonably close (depending on how we tune). We won't have false positives (like with a bloom filter) -- we'll have a degree of error (i.e. the actual count may be 1000, but the HLL reports 1004).
HyperLogLog provides a probabilistic data structure that is good at counting _distinct_ entries, so that means that the count _will not_ be exact, but be reasonably close (depending on how we tune). We won't have false positives (like with a bloom filter) -- we'll have a degree of error (i.e. the actual count may be 1000, but the HLL reports 1004).
We have to take this into account on the UI side but and maybe retrieve the full count if anyone ever _really_ needs to know/view individual users that have seen the content, so we can fall back to our association table there.
@@ -357,7 +357,7 @@ export class AppRoutingModule {}
Our app will start with the login screen, after which we can move to the workspace with our boards and finally dive into one specific board to show all its lists and cards.
To correclty use the Angular router we can now update the **src/app/app.component.html** so it only holds one line:
To correctly use the Angular router we can now update the **src/app/app.component.html** so it only holds one line:
```html
<router-outlet></router-outlet>
@@ -721,7 +721,7 @@ In fact that's enough for our first interaction with our Supabase tables, so we
Additionally we want to add a board, and here we encounter one of those _real world problems_:
Because we have a **database trigger** that adds an entry when a new table is added, the user is not immediately authroized to access the new board row! Only once the trigger has finished, the RLS that checks user boards can confirm that this user is part of the board.
Because we have a **database trigger** that adds an entry when a new table is added, the user is not immediately authorized to access the new board row! Only once the trigger has finished, the RLS that checks user boards can confirm that this user is part of the board.
Therefore we add another line to load the boards again and pop the last added element so we can automatically navigate into its details page.
@@ -981,7 +981,7 @@ To keep track of data and changes we hold all cards in the `listCards` object th
In terms of additional logic we might want to update or delete the board, which we can do simply with the previously created service functions.
Same is true for lists and cards, whcih can be added, updated or removed.
Same is true for lists and cards, which can be added, updated or removed.
However, this will not (yet) update our local data, since we want to implement this with realtime updates later.
@@ -124,7 +124,7 @@ Our friends from Netlify invited Ant to their new webinar series. He and Netlify
- Supabase Crash Course by The Net Ninja. [Video Courses](https://www.youtube.com/watch?v=ydz7Dj5QHKY&list=PL4cUxeGkcC9hUb6sHthUEwG7r9VDPBMKO)
- How to build a Grocery Application with Webflow CMS using DhiWise. [Tutorial](https://dev.to/saloni137/how-to-build-a-grocery-application-with-webflow-cms-using-dhiwise-1a72)
- How To Create a Full Stack app with SolidJS, Supabase, and TailwindCSS [Video and Tutorial.](https://blog.chetanverma.com/how-to-create-a-full-stack-app-with-solidjs-supabase-and-tailwindcss)
- The WalletConnect Cloud now supports Sign in wtih Ethereum. [Announcement](https://twitter.com/TheHarryET/status/1559861021845643265).
- The WalletConnect Cloud now supports Sign in with Ethereum. [Announcement](https://twitter.com/TheHarryET/status/1559861021845643265).
- Building In Public: Cartta Tech Stack. [Article](https://dev.to/fvaldes33/building-in-public-cartta-tech-stack-5en0)
- Supabase + Vue 3 in 12 minutes. [Video](https://www.youtube.com/watch?v=YN32uVqAXw8&feature=emb_title)
+1 -1
View File
@@ -52,7 +52,7 @@ const Announcement = () => {
<div
onClick={handleLink}
className="
launch-week-gradientBg--anouncement-bar
launch-week-gradientBg--announcement-bar
to-green-1000
hover:from-green-1000
hover:to-green-1100 relative flex
+3 -3
View File
@@ -280,7 +280,7 @@ launch week
}
}
.launch-week-gradientBg--anouncement-bar {
.launch-week-gradientBg--announcement-bar {
background-image: url('/images/launchweek/supabase-launch-week-5-bg.jpg');
background-color: hsl(0, 0%, 11%);
width: 100%;
@@ -291,13 +291,13 @@ launch week
background-repeat: no-repeat;
}
.dark .launch-week-gradientBg--anouncement-bar {
.dark .launch-week-gradientBg--announcement-bar {
background-image: url('/images/launchweek/supabase-launch-week-5-bg.jpg');
background-color: #1c1c1c;
}
@media screen and (min-width: 1032px) {
.launch-week-gradientBg--anouncement-bar {
.launch-week-gradientBg--announcement-bar {
background-position-y: -780px;
}
}
+2 -2
View File
@@ -1337,7 +1337,7 @@
"isExported": true
},
"comment": {
"shortText": "Retuns `true` is the connection is open."
"shortText": "Returns `true` is the connection is open."
},
"type": {
"type": "intrinsic",
@@ -1421,7 +1421,7 @@
},
"comment": {
"shortText": "Logs the message.",
"text": "For customized logging, `this.logger` can be overriden.\n"
"text": "For customized logging, `this.logger` can be overridden.\n"
},
"parameters": [
{
@@ -1811,7 +1811,7 @@
"isExported": true
},
"comment": {
"shortText": "Retuns `true` is the connection is open."
"shortText": "Returns `true` is the connection is open."
},
"type": {
"type": "intrinsic",
@@ -1895,7 +1895,7 @@
},
"comment": {
"shortText": "Logs the message.",
"text": "For customized logging, `this.logger` can be overriden.\n"
"text": "For customized logging, `this.logger` can be overridden.\n"
},
"parameters": [
{
@@ -6924,7 +6924,7 @@
"isExported": true
},
"comment": {
"shortText": "Retuns `true` is the connection is open."
"shortText": "Returns `true` is the connection is open."
},
"type": {
"type": "intrinsic",
@@ -7008,7 +7008,7 @@
},
"comment": {
"shortText": "Logs the message.",
"text": "For customized logging, `this.logger` can be overriden.\n"
"text": "For customized logging, `this.logger` can be overridden.\n"
},
"parameters": [
{
@@ -11979,7 +11979,7 @@
"isExported": true
},
"comment": {
"shortText": "Retuns `true` is the connection is open."
"shortText": "Returns `true` is the connection is open."
},
"type": {
"type": "intrinsic",
@@ -12063,7 +12063,7 @@
},
"comment": {
"shortText": "Logs the message.",
"text": "For customized logging, `this.logger` can be overriden.\n"
"text": "For customized logging, `this.logger` can be overridden.\n"
},
"parameters": [
{
+3 -3
View File
@@ -3467,7 +3467,7 @@
"kindString": "Call signature",
"flags": {},
"comment": {
"shortText": "Retuns `true` is the connection is open."
"shortText": "Returns `true` is the connection is open."
},
"type": {
"type": "intrinsic",
@@ -3498,7 +3498,7 @@
"flags": {},
"comment": {
"shortText": "Logs the message.",
"text": "For customized logging, `this.logger` can be overriden.\n"
"text": "For customized logging, `this.logger` can be overridden.\n"
},
"parameters": [
{
@@ -4108,7 +4108,7 @@
"isOptional": true
},
"comment": {
"shortText": "self option enables client to receive message it broadcast\nack option instructs server to acknowlege that broadcast message was received"
"shortText": "self option enables client to receive message it broadcast\nack option instructs server to acknowledge that broadcast message was received"
},
"sources": [
{