PR/Issue | Owner | Summary |
---|---|---|
#1829 | @MikeRalphson | Scopes in non-oauth2 securitySchemes. Use of term 'scope', should we allow definition of allowed/expected scopes at the securityScheme level for all types? |
#2181 | @MikeRalphson | $ref siblings. SHOULD or MUST for behaviour, reference to OAS structure not OAS document object instance |
{ | |
"id": "automl:v1beta1", | |
"documentationLink": "https://cloud.google.com/automl", | |
"revision": "20200315", | |
"discoveryVersion": "v1", | |
"version_module": true, | |
"schemas": { | |
"StructType": { | |
"description": "`StructType` defines the DataType-s of a STRUCT type.", | |
"type": "object", |
{ | |
"id": "https://spec.openapis.org/oas/3.0/schema/2019-04-02", | |
"$schema": "http://json-schema.org/draft-04/schema#", | |
"description": "Validation schema for OpenAPI Specification 3.0.X.", | |
"type": "object", | |
"required": [ | |
"openapi", | |
"info", | |
"paths" | |
], |
Given
schemas:
foo:
type: object
xml:
name: MyFoo
properties:
bar:
From
https://github.com/Mermade/openapi-specification-extensions/blob/master/refs/combined.csv
we can see that the vast majority of uses (at the time the survey was run) are for description
on it's own,
description
with some x-extension
or for schema-related keywords - this latter case is no longer a concern as we
delegate the behaviour of $ref
in schemaObjects to JSON Schema rules.
What are the candidates for $ref siblings?
Array.prototype.foo = function() { return 'Still callable'; }; | |
function test() { | |
let count = 0; | |
for (const e in []) { | |
console.log('Found '+e); | |
count++; | |
Object.defineProperty(Array.prototype, e, { | |
value: Array.prototype[e], | |
enumerable: false |
This is Google's cache of https://learnxinyminutes.com/docs/go/. It is a snapshot of the page as it appeared on 21 Feb 2019 18:16:43 GMT. The current page could have changed in the meantime. Learn more. Full versionText-only versionView source Tip: To quickly find your search term on this page, press Ctrl+F or ⌘-F (Mac) and use the find bar. Share this page Select theme: Learn X in Y minutes Where X=Go
Get the code: learngo.go
The goal of this is to have an easily-scannable reference for the most common syntax idioms in JavaScript and Rust so that programmers most comfortable with JavaScript can quickly get through the syntax differences and feel like they could read and write basic Rust programs.
What do you think? Does this meet its goal? If not, why not?
JavaScript:
- MongoDB - for MQTT testing. Stoppable/startable with
service mongodb
overlay: 1.0.0 | |
info: | |
version: 1.0.0 | |
title: HTTP Status Codes German translation | |
contact: | |
email: [email protected] | |
url: 'https://mermade.org.uk' | |
name: Mike Ralphson | |
x-twitter: PermittedSoc | |
license: |