Fix various typos

Found via `codespell -q 3 -S CHANGELOG.md -L doesnt,optio,promisses,tread,usera`
This commit is contained in:
luz paz
2022-04-15 13:49:46 -04:00
parent b0395a5cf1
commit 915cb0afaf
12 changed files with 15 additions and 15 deletions
+1 -1
View File
@@ -81,7 +81,7 @@ module.exports = class IFCParser {
spcklFaces.push(raw.indices[i])
}
// Create a propper Speckle Mesh
// Create a proper Speckle Mesh
const spcklMesh = {
speckle_type: 'Objects.Geometry.Mesh',
units: 'm',
@@ -189,7 +189,7 @@ export default {
}
},
mounted() {
// for some reasons, these are not clearly intialised
// for some reasons, these are not clearly initialised
this.users = []
this.selectedIds = []
this.selectionCenter = null
@@ -61,7 +61,7 @@
:style="`${stickyTop ? 'position: sticky; top: 128px;' : ''} z-index: 6`"
/>
<div v-if="topFilters.length !== 0 && !filterSearch">
<v-subheader>Reccommended filters:</v-subheader>
<v-subheader>Recommended filters:</v-subheader>
<div v-for="(filter, index) in topFilters" :key="index">
<filter-row-select
v-if="filter"
@@ -148,7 +148,7 @@ export default {
if (this.$route.query.emailverfiedstatus) {
setTimeout(() => {
this.$eventHub.$emit('notification', {
text: '✉️ Email succesfully verfied!'
text: '✉️ Email successfully verfied!'
})
}, 1000) // todo: ask fabian if there's a better way, feels icky
}
@@ -7,7 +7,7 @@
Great! All invites were sent.
</v-alert>
<v-alert v-show="errors.length !== 0" prominent dismissible type="error">
<p>Invite send failed for adresses:</p>
<p>Invite send failed for addresses:</p>
<ul>
<li v-for="error in errors" :key="error.email">
{{ error.email }}: {{ error.reason }}
@@ -62,7 +62,7 @@
</v-chip>
</template>
</v-combobox>
<p v-if="!selectedStream">Optionaly invite users to stream.</p>
<p v-if="!selectedStream">Optionally invite users to stream.</p>
<stream-search-bar
v-if="!selectedStream"
:gotostreamonclick="false"
@@ -26,7 +26,7 @@
<h2>There are no global variables in this stream.</h2>
<p class="caption">
Global variables can hold various information that's useful across the project:
location (city, adress, lat & long coordinates), custom project names or tags,
location (city, address, lat & long coordinates), custom project names or tags,
or any other numbers or text that you want to keep track of.
</p>
<template #actions>
@@ -1,7 +1,7 @@
extend type Query {
comment(id: String!, streamId: String!): Comment
"""
This query can be used in the follwing ways:
This query can be used in the following ways:
- get all the comments for a stream: **do not pass in any resource identifiers**.
- get the comments targeting any of a set of provided resources (comments/objects): **pass in an array of resources.**
"""
@@ -70,7 +70,7 @@ describe('Server Invites @server-invites', () => {
expect(err.message).to.equal('Already invited!')
})
})
it('low multiple invites for the same email regardles of casing', async () => {
it('low multiple invites for the same email regardless of casing', async () => {
await createAndSendInvite({
email: 'dIdImItrIe@gmaIl.com',
inviterId: actor.id,
+1 -1
View File
@@ -72,7 +72,7 @@ The 3 optional parameters are:
- `colorBy`: A dictionary that makes all objects colored based on a property value. Two types of coloring are supported:
- Gradient (from a numeric property): `{ 'type': 'gradient', 'property': propertyName, 'minValue': propertyMinValue, 'maxValue': propertyMaxValue, 'gradientColors': [color1, color2], default: colorForObjectsWithMissingProperty }`
- Category (for coloring each unique value differently): `{ 'type': 'category', 'property': propertyName, 'values': { value1: color1, value2: color2, ... }, 'default': colorForAnyOtherValue }`. The `values` and the `default` parameters are optional: Random colors are generated if they are ommited.
- Category (for coloring each unique value differently): `{ 'type': 'category', 'property': propertyName, 'values': { value1: color1, value2: color2, ... }, 'default': colorForAnyOtherValue }`. The `values` and the `default` parameters are optional: Random colors are generated if they are omitted.
- `ghostOthers`: A boolean (default `false`). If set to `true`, then the objects that are filtered out are actually shown with very low opacity, so that the remaining objects have a better context.
@@ -47,8 +47,8 @@ async function makeNetworkRequest({ url, data, headersData }) {
body: JSON.stringify(data),
headers,
follow: 2, // follow max 2 redirects (fetch defaults to 20)
timeout: 10 * 1000, // timeout after 10sec (defauls to no timeout)
size: 500 * 1000 // 500kb max response size, to accomodate various error responses (defaults to no limit)
timeout: 10 * 1000, // timeout after 10sec (defaults to no timeout)
size: 500 * 1000 // 500kb max response size, to accommodate various error responses (defaults to no limit)
}).then(async (res) => ({ status: res.status, body: await res.text() }))
//console.log( 'Server response:', response )
+2 -2
View File
@@ -7,7 +7,7 @@ type: application
# to the chart and its templates, including the app version.
# Versions are expected to follow Semantic Versioning (https://semver.org/)
# Set by the build process to the corect value
# Set by the build process to the correct value
# version: 0.1.0
# This is the version number of the application being deployed. This version number should be
@@ -15,5 +15,5 @@ type: application
# follow Semantic Versioning. They should reflect the version the application is using.
# It is recommended to use it with quotes.
# Set by the build process to the corect value
# Set by the build process to the correct value
# appVersion: "2.3.3"
+1 -1
View File
@@ -34,7 +34,7 @@
},
],
"settings": {
// Some settings below are duplicated in root/.vscode, incase the repo is opened without targetting the workspace file
// Some settings below are duplicated in root/.vscode, incase the repo is opened without targeting the workspace file
// I don't think there's a way to force users to open the project as a workspace always
"explorer.confirmDelete": false,
"files.associations": {