File tree 3 files changed +7
-7
lines changed
python/ql/lib/semmle/python/dataflow/new/internal
ruby/ql/lib/codeql/ruby/typetracking 3 files changed +7
-7
lines changed Original file line number Diff line number Diff line change @@ -185,7 +185,7 @@ module StepSummary {
185
185
}
186
186
187
187
/**
188
- * Holds if `nodeFrom` is being written to the `content` content of the object in `nodeTo`.
188
+ * Holds if `nodeFrom` is being written to the `contents` of the object in `nodeTo`.
189
189
*
190
190
* Note that `nodeTo` will always be a local source node that flows to the place where the content
191
191
* is written in `basicStoreStep`. This may lead to the flow of information going "back in time"
@@ -204,7 +204,7 @@ module StepSummary {
204
204
* def bar(x):
205
205
* z = x.attr
206
206
* ```
207
- * for the attribute write `x.attr = y`, we will have `content ` being the literal string `"attr"`,
207
+ * for the attribute write `x.attr = y`, we will have `contents ` being the literal string `"attr"`,
208
208
* `nodeFrom` will be `y`, and `nodeTo` will be the object `Foo()` created on the first line of the
209
209
* function. This means we will track the fact that `x.attr` can have the type of `y` into the
210
210
* assignment to `z` inside `bar`, even though this attribute write happens _after_ `bar` is called.
Original file line number Diff line number Diff line change @@ -185,7 +185,7 @@ module StepSummary {
185
185
}
186
186
187
187
/**
188
- * Holds if `nodeFrom` is being written to the `content` content of the object in `nodeTo`.
188
+ * Holds if `nodeFrom` is being written to the `contents` of the object in `nodeTo`.
189
189
*
190
190
* Note that `nodeTo` will always be a local source node that flows to the place where the content
191
191
* is written in `basicStoreStep`. This may lead to the flow of information going "back in time"
@@ -204,7 +204,7 @@ module StepSummary {
204
204
* def bar(x):
205
205
* z = x.attr
206
206
* ```
207
- * for the attribute write `x.attr = y`, we will have `content ` being the literal string `"attr"`,
207
+ * for the attribute write `x.attr = y`, we will have `contents ` being the literal string `"attr"`,
208
208
* `nodeFrom` will be `y`, and `nodeTo` will be the object `Foo()` created on the first line of the
209
209
* function. This means we will track the fact that `x.attr` can have the type of `y` into the
210
210
* assignment to `z` inside `bar`, even though this attribute write happens _after_ `bar` is called.
Original file line number Diff line number Diff line change @@ -117,11 +117,11 @@ predicate returnStep(Node nodeFrom, Node nodeTo) {
117
117
}
118
118
119
119
/**
120
- * Holds if `nodeFrom` is being written to the `content` content of the object
120
+ * Holds if `nodeFrom` is being written to the `contents` of the object
121
121
* in `nodeTo`.
122
122
*
123
123
* Note that the choice of `nodeTo` does not have to make sense
124
- * "chronologically". All we care about is whether the `content` content of
124
+ * "chronologically". All we care about is whether the `contents` of
125
125
* `nodeTo` can have a specific type, and the assumption is that if a specific
126
126
* type appears here, then any access of that particular content can yield
127
127
* something of that particular type.
@@ -140,7 +140,7 @@ predicate returnStep(Node nodeFrom, Node nodeTo) {
140
140
* z = x.content
141
141
* end
142
142
* ```
143
- * for the content write `x.content = y`, we will have `content ` being the
143
+ * for the content write `x.content = y`, we will have `contents ` being the
144
144
* literal string `"content"`, `nodeFrom` will be `y`, and `nodeTo` will be the
145
145
* `Foo` object created on the first line of the function. This means we will
146
146
* track the fact that `x.content` can have the type of `y` into the assignment
You can’t perform that action at this time.
0 commit comments