Keyboard Shortcuts

File
u :up to issue
m :publish + mail comments
M :edit review message
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
<Enter> :respond to / edit current comment
d :mark current comment as done
Issue
u :up to list of issues
m :publish + mail comments
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
# : close issue
Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :save comment
<Esc> :cancel edit
Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(127)
Issues Repositories Search
Open Issues | Closed Issues | All Issues | Sign in with your Google Account to create issues and add comments

Issue 3275: message condition params with a single, value-less pair

Can't Edit
Can't Publish+Mail
Start Review
Created:
17 years, 4 months ago by markluffel
Modified:
2 years, 2 months ago
Reviewers:
azuercher, tparikh
Base URL:
https://svn.appcelerator.org/appcelerator_sdk/trunk/components/websdk/src/js/
Visibility:
Public.

Patch Set 1 #

Created: 17 years, 4 months ago
Download [raw] [tar.bz2]
Unified diffs Side-by-side diffs Delta from patch set Stats (+4 lines, -2 lines) Patch
compiler.js View 1 chunk +4 lines, -2 lines 1 comment Download
Total messages: 1
|
markluffel
So, Alex was telling me about the code review process that his team does, and ...
17 years, 4 months ago (2008年08月27日 01:24:13 UTC) #1
So, Alex was telling me about the code review process that his team does, and I
checked out this thing that Guido, the creator of Python wrote.
It seems pretty sane and usable thus far, though for contract work, we'd
probably want to deploy a different copy of the source (it's open) rather than
use the default deployment (which is public).
There's nothing particularly interesting about this patch, I just needed
something to upload and had it outstanding.
Opinions on code review?
http://codereview.appspot.com/3275/diff/1/2
File compiler.js (right):
http://codereview.appspot.com/3275/diff/1/2#newcode2721
Line 2721: return [{key:str,value:'',empty:true}];
empty strings evaluate to false, don't we want a value that will be true (to
indicate that there was a key of that name (since presumably, keys without
values are either boolean flags or special strings for which the value doesn't
matter at all))?
Sign in to reply to this message.
|
Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b

AltStyle によって変換されたページ (->オリジナル) /