chrome/common/extensions/docs/templates/private/availability_messages.html - Issue 18323018: Linking AvailabilityFinder with APIDataSource and intro-table templates.

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/common/extensions/docs/templates/private/availability_messages.html

Issue 18323018: Linking AvailabilityFinder with APIDataSource and intro-table templates. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: More Generic Templates Created 7 years, 5 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

« chrome/common/extensions/docs/templates/json/intro_tables.json ('K') | « chrome/common/extensions/docs/templates/json/intro_tables.json ('k') | chrome/common/extensions/docs/templates/private/intro_table.html » ('j') | chrome/common/extensions/docs/templates/private/intro_table.html » ('J')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
(Empty)
	1 {{#message}}

	2 {{?stable}}

	3 Stable since version {{version}}.
	not at google - send to devlin 2013/07/16 22:25:00 Stable since Chrome {{version}}. Also could you a Stable since Chrome {{version}}. Also could you add {{- TODO(epeterson): link to the entry in What's New page once it's generated. -}} epeterson 2013/07/17 23:48:23 Done. Show quoted text On 2013/07/16 22:25:00, kalman wrote: > Stable since Chrome {{version}}. > > Also could you add > > {{- TODO(epeterson): link to the entry in What's New page once it's generated. > -}} Done.
	4 {{/stable}}

	5 {{?beta}}

	6 <a href="https://www.google.com/landing/chrome/beta/">Beta</a> and <a href=" http://www.chromium.org/getting-involved/dev-channel">dev</a> channels only.

	7 {{/beta}}

	8 {{?dev}}

	9 <a href="http://www.chromium.org/getting-involved/dev-channel">Dev</a> chann el only.

	10 {{/dev}}

	11 {{?trunk}}

	12 Only when <a href="http://www.chromium.org/developers/">built from source</a >.

	13 {{/trunk}}

	14 {{?experimental}}

	15 Experimental only (see <a href="experimental.html#using">How to use experime ntal APIs</a>).

	16 {{/experimental}}

	17 {{/message}}
	epeterson 2013/07/16 00:28:23 All of the possible availability messages were put All of the possible availability messages were put into this file to keep them nice and tidy. This template will have a content node from the intro_list passed into it, so it 'knows' which message to display and has access to the version if an API is 'stable.' not at google - send to devlin 2013/07/16 22:25:00 yeah so I'll comment in the data source. we'd need Show quoted text On 2013/07/16 00:28:23, epeterson wrote: > All of the possible availability messages were put into this file to keep them > nice and tidy. > > This template will have a content node from the intro_list passed into it, so it > 'knows' which message to display and has access to the version if an API is > 'stable.' yeah so I'll comment in the data source. we'd need to pull the "stable since Chrome {{version}}: into a separate partial but other than that they're all there. may also need to pull the wording out into separate partials? epeterson 2013/07/17 23:48:23 Done. Show quoted text On 2013/07/16 22:25:00, kalman wrote: > On 2013/07/16 00:28:23, epeterson wrote: > > All of the possible availability messages were put into this file to keep them > > nice and tidy. > > > > This template will have a content node from the intro_list passed into it, so > it > > 'knows' which message to display and has access to the version if an API is > > 'stable.' > > yeah so I'll comment in the data source. we'd need to pull the "stable since > Chrome {{version}}: into a separate partial but other than that they're all > there. > > may also need to pull the wording out into separate partials? Done.
OLD	NEW