File tree Expand file tree Collapse file tree
python/ql/lib/semmle/python/dataflow/new/internal
ruby/ql/lib/codeql/ruby/typetracking Expand file tree Collapse file tree Original file line number Diff line number Diff line change @@ -185,7 +185,7 @@ module StepSummary {
185185 }
186186
187187 /**
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`.
189189 *
190190 * Note that `nodeTo` will always be a local source node that flows to the place where the content
191191 * is written in `basicStoreStep`. This may lead to the flow of information going "back in time"
@@ -204,7 +204,7 @@ module StepSummary {
204204 * def bar(x):
205205 * z = x.attr
206206 * ```
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"`,
208208 * `nodeFrom` will be `y`, and `nodeTo` will be the object `Foo()` created on the first line of the
209209 * function. This means we will track the fact that `x.attr` can have the type of `y` into the
210210 * 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 {
185185 }
186186
187187 /**
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`.
189189 *
190190 * Note that `nodeTo` will always be a local source node that flows to the place where the content
191191 * is written in `basicStoreStep`. This may lead to the flow of information going "back in time"
@@ -204,7 +204,7 @@ module StepSummary {
204204 * def bar(x):
205205 * z = x.attr
206206 * ```
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"`,
208208 * `nodeFrom` will be `y`, and `nodeTo` will be the object `Foo()` created on the first line of the
209209 * function. This means we will track the fact that `x.attr` can have the type of `y` into the
210210 * 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 @@ -122,11 +122,11 @@ predicate returnStep(Node nodeFrom, Node nodeTo) {
122122}
123123
124124/**
125- * Holds if `nodeFrom` is being written to the `content` content of the object
125+ * Holds if `nodeFrom` is being written to the `contents` of the object
126126 * in `nodeTo`.
127127 *
128128 * Note that the choice of `nodeTo` does not have to make sense
129- * "chronologically". All we care about is whether the `content` content of
129+ * "chronologically". All we care about is whether the `contents` of
130130 * `nodeTo` can have a specific type, and the assumption is that if a specific
131131 * type appears here, then any access of that particular content can yield
132132 * something of that particular type.
@@ -145,7 +145,7 @@ predicate returnStep(Node nodeFrom, Node nodeTo) {
145145 * z = x.content
146146 * end
147147 * ```
148- * for the content write `x.content = y`, we will have `content ` being the
148+ * for the content write `x.content = y`, we will have `contents ` being the
149149 * literal string `"content"`, `nodeFrom` will be `y`, and `nodeTo` will be the
150150 * `Foo` object created on the first line of the function. This means we will
151151 * 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