chrome/test/data/extensions/managed_extension/schema/managed_storage.json - Issue 14587009: Added a PolicyManifestHandler.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: chrome/test/data/extensions/managed_extension/schema/managed_storage.json

Issue 14587009: Added a PolicyManifestHandler. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: rebase Created 7 years, 7 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

« chrome/common/extensions/api/_manifest_features.json ('K') | « chrome/test/data/extensions/managed_extension/manifest.json ('k') | chrome/test/data/extensions/managed_extension2/managed_storage_schema.json » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
(Empty)
	1 {

	2 "$schema": "http://json-schema.org/draft-03/schema#",
	not at google - send to devlin 2013/05/23 16:56:18 just curious but is there any particular reason th just curious but is there any particular reason this needs to end with a #? Joao da Silva 2013/05/24 21:31:49 Yes; thanks for asking 'cause I had forgotten abou Show quoted text On 2013/05/23 16:56:18, kalman wrote: > just curious but is there any particular reason this needs to end with a #? Yes; thanks for asking 'cause I had forgotten about it :-) Reason 1: forward compatibility. The latest spec defines well-known $schema constants, and this is the constant for v3. See http://json-schema.org/latest/json-schema-core.html#anchor22. Reason 2: this value is a valid URL that can be used to resolve a schema that describes the schema, used for hyper-schemas. If you open this URL you'll see that it declares its ID with this constant. not at google - send to devlin 2013/05/25 00:50:57 It would still be a a valid URL, and in fact the e Show quoted text On 2013/05/24 21:31:49, Joao da Silva wrote: > On 2013/05/23 16:56:18, kalman wrote: > > just curious but is there any particular reason this needs to end with a #? > > Yes; thanks for asking 'cause I had forgotten about it :-) > > Reason 1: forward compatibility. The latest spec defines well-known $schema > constants, and this is the constant for v3. See > http://json-schema.org/latest/json-schema-core.html#anchor22. > > Reason 2: this value is a valid URL that can be used to resolve a schema that > describes the schema, used for hyper-schemas. If you open this URL you'll see > that it declares its ID with this constant. It would still be a a valid URL, and in fact the equivalent URL, without the # though. It's odd to me that it's there. But the site you point out says to use it, so, cool.
	3 "type": "object",

	4 "properties": {

	5 "Name": {

	6 "type": "string"

	7 },

	8 "Another": {

	9 "type": "string"

	10 }

	11 }

	12 }

OLD	NEW