kotovalexarian-likes-github
/
jashkenas--coffeescript
mirror of https://github.com/jashkenas/coffeescript.git
1
0
Fork 0
Code Releases Activity
jashkenas--coffeescript/test/abstract_syntax_tree_locati...

411 lines
8.7 KiB
CoffeeScript
Raw Normal View History

AST generation hooks (#5099) * include range in location data * use exclusive ranges * ast generation hooks * fix getAstChildren() * babylon - * isArray -> Array.isArray * pass options to toJSON() * default astType on Base * using exclusive range * extract location data tests * babylon -> ast * remove do -> * _toAst -> getAstContent * Pass through parsed number value from lexer to node; don't process more than is necessary (a number literal can never be negative, because the negative sign is an Op token and node) * normalize NumberLiteral values * use parsedValue in getNumberValue() * recursive getNumberValue() * parseNumber() * The core JavaScript Number constructor does a better job at parsing strings into numbers than our helper does * Use Object.assign rather than merge or extend * Update link * Cleanup style * Refactor to make AST generation more object-oriented: have each of the AST properties be generated on the node itself, rather than in loops in the base class * Untangle test helpers: give the AST location tests their own specific helper function, and move the general AST helper functions into the main AST tests file * Not passing o * Add node type check to AST location data tests
2018-09-17 17:40:37 +00:00
# Astract Syntax Tree location data
# ---------------------------------
testAstLocationData = (code, expected) ->
We don't need to abstract a new helpers file for just three lines of code, there's more code required to pull this in where it's needed than to just duplicate the two lines of code we need in both places where these 'shared' helpers are currently used
2018-09-23 05:20:58 +00:00
ast = CoffeeScript.compile code, ast: yes
testAstNodeLocationData ast.expressions[0], expected
AST generation hooks (#5099) * include range in location data * use exclusive ranges * ast generation hooks * fix getAstChildren() * babylon - * isArray -> Array.isArray * pass options to toJSON() * default astType on Base * using exclusive range * extract location data tests * babylon -> ast * remove do -> * _toAst -> getAstContent * Pass through parsed number value from lexer to node; don't process more than is necessary (a number literal can never be negative, because the negative sign is an Op token and node) * normalize NumberLiteral values * use parsedValue in getNumberValue() * recursive getNumberValue() * parseNumber() * The core JavaScript Number constructor does a better job at parsing strings into numbers than our helper does * Use Object.assign rather than merge or extend * Update link * Cleanup style * Refactor to make AST generation more object-oriented: have each of the AST properties be generated on the node itself, rather than in loops in the base class * Untangle test helpers: give the AST location tests their own specific helper function, and move the general AST helper functions into the main AST tests file * Not passing o * Add node type check to AST location data tests
2018-09-17 17:40:37 +00:00
test nested location data
2018-09-17 16:27:30 +00:00
testAstNodeLocationData = (node, expected, path = '') ->
extendPath = (additionalPath) ->
return additionalPath unless path
"#{path}.#{additionalPath}"
ok node?, "Missing expected node at '#{path}'"
testSingleNodeLocationData node, expected, path if expected.range?
for own key, expectedChild of expected when key not in ['start', 'end', 'range', 'loc']
if Array.isArray expectedChild
ok Array.isArray(node[key]), "Missing expected array at '#{extendPath key}'"
for expectedItem, index in expectedChild
testAstNodeLocationData node[key][index], expectedItem, extendPath "#{key}[#{index}]"
else if typeof expectedChild is 'object'
testAstNodeLocationData node[key], expectedChild, extendPath key
testSingleNodeLocationData = (node, expected, path) ->
pathStr = if path then " at '#{path}'" else ''
AST generation hooks (#5099) * include range in location data * use exclusive ranges * ast generation hooks * fix getAstChildren() * babylon - * isArray -> Array.isArray * pass options to toJSON() * default astType on Base * using exclusive range * extract location data tests * babylon -> ast * remove do -> * _toAst -> getAstContent * Pass through parsed number value from lexer to node; don't process more than is necessary (a number literal can never be negative, because the negative sign is an Op token and node) * normalize NumberLiteral values * use parsedValue in getNumberValue() * recursive getNumberValue() * parseNumber() * The core JavaScript Number constructor does a better job at parsing strings into numbers than our helper does * Use Object.assign rather than merge or extend * Update link * Cleanup style * Refactor to make AST generation more object-oriented: have each of the AST properties be generated on the node itself, rather than in loops in the base class * Untangle test helpers: give the AST location tests their own specific helper function, and move the general AST helper functions into the main AST tests file * Not passing o * Add node type check to AST location data tests
2018-09-17 17:40:37 +00:00
# Even though it’s not part of the location data, check the type to ensure
# that we’re testing the node we think we are.
test nested location data
2018-09-17 16:27:30 +00:00
if expected.type?
eq node.type, expected.type, \
"Expected AST node type #{reset}#{node.type}#{red} to equal #{reset}#{expected.type}#{red}"
AST generation hooks (#5099) * include range in location data * use exclusive ranges * ast generation hooks * fix getAstChildren() * babylon - * isArray -> Array.isArray * pass options to toJSON() * default astType on Base * using exclusive range * extract location data tests * babylon -> ast * remove do -> * _toAst -> getAstContent * Pass through parsed number value from lexer to node; don't process more than is necessary (a number literal can never be negative, because the negative sign is an Op token and node) * normalize NumberLiteral values * use parsedValue in getNumberValue() * recursive getNumberValue() * parseNumber() * The core JavaScript Number constructor does a better job at parsing strings into numbers than our helper does * Use Object.assign rather than merge or extend * Update link * Cleanup style * Refactor to make AST generation more object-oriented: have each of the AST properties be generated on the node itself, rather than in loops in the base class * Untangle test helpers: give the AST location tests their own specific helper function, and move the general AST helper functions into the main AST tests file * Not passing o * Add node type check to AST location data tests
2018-09-17 17:40:37 +00:00
eq node.start, expected.start, \
test nested location data
2018-09-17 16:27:30 +00:00
"Expected location start #{reset}#{node.start}#{red} to equal #{reset}#{expected.start}#{red}#{pathStr}"
AST generation hooks (#5099) * include range in location data * use exclusive ranges * ast generation hooks * fix getAstChildren() * babylon - * isArray -> Array.isArray * pass options to toJSON() * default astType on Base * using exclusive range * extract location data tests * babylon -> ast * remove do -> * _toAst -> getAstContent * Pass through parsed number value from lexer to node; don't process more than is necessary (a number literal can never be negative, because the negative sign is an Op token and node) * normalize NumberLiteral values * use parsedValue in getNumberValue() * recursive getNumberValue() * parseNumber() * The core JavaScript Number constructor does a better job at parsing strings into numbers than our helper does * Use Object.assign rather than merge or extend * Update link * Cleanup style * Refactor to make AST generation more object-oriented: have each of the AST properties be generated on the node itself, rather than in loops in the base class * Untangle test helpers: give the AST location tests their own specific helper function, and move the general AST helper functions into the main AST tests file * Not passing o * Add node type check to AST location data tests
2018-09-17 17:40:37 +00:00
eq node.end, expected.end, \
test nested location data
2018-09-17 16:27:30 +00:00
"Expected location end #{reset}#{node.end}#{red} to equal #{reset}#{expected.end}#{red}#{pathStr}"
AST generation hooks (#5099) * include range in location data * use exclusive ranges * ast generation hooks * fix getAstChildren() * babylon - * isArray -> Array.isArray * pass options to toJSON() * default astType on Base * using exclusive range * extract location data tests * babylon -> ast * remove do -> * _toAst -> getAstContent * Pass through parsed number value from lexer to node; don't process more than is necessary (a number literal can never be negative, because the negative sign is an Op token and node) * normalize NumberLiteral values * use parsedValue in getNumberValue() * recursive getNumberValue() * parseNumber() * The core JavaScript Number constructor does a better job at parsing strings into numbers than our helper does * Use Object.assign rather than merge or extend * Update link * Cleanup style * Refactor to make AST generation more object-oriented: have each of the AST properties be generated on the node itself, rather than in loops in the base class * Untangle test helpers: give the AST location tests their own specific helper function, and move the general AST helper functions into the main AST tests file * Not passing o * Add node type check to AST location data tests
2018-09-17 17:40:37 +00:00
arrayEq node.range, expected.range, \
test nested location data
2018-09-17 16:27:30 +00:00
"Expected location range #{reset}#{JSON.stringify node.range}#{red} to equal #{reset}#{JSON.stringify expected.range}#{red}#{pathStr}"
AST generation hooks (#5099) * include range in location data * use exclusive ranges * ast generation hooks * fix getAstChildren() * babylon - * isArray -> Array.isArray * pass options to toJSON() * default astType on Base * using exclusive range * extract location data tests * babylon -> ast * remove do -> * _toAst -> getAstContent * Pass through parsed number value from lexer to node; don't process more than is necessary (a number literal can never be negative, because the negative sign is an Op token and node) * normalize NumberLiteral values * use parsedValue in getNumberValue() * recursive getNumberValue() * parseNumber() * The core JavaScript Number constructor does a better job at parsing strings into numbers than our helper does * Use Object.assign rather than merge or extend * Update link * Cleanup style * Refactor to make AST generation more object-oriented: have each of the AST properties be generated on the node itself, rather than in loops in the base class * Untangle test helpers: give the AST location tests their own specific helper function, and move the general AST helper functions into the main AST tests file * Not passing o * Add node type check to AST location data tests
2018-09-17 17:40:37 +00:00
eq node.loc.start.line, expected.loc.start.line, \
test nested location data
2018-09-17 16:27:30 +00:00
"Expected location start line #{reset}#{node.loc.start.line}#{red} to equal #{reset}#{expected.loc.start.line}#{red}#{pathStr}"
AST generation hooks (#5099) * include range in location data * use exclusive ranges * ast generation hooks * fix getAstChildren() * babylon - * isArray -> Array.isArray * pass options to toJSON() * default astType on Base * using exclusive range * extract location data tests * babylon -> ast * remove do -> * _toAst -> getAstContent * Pass through parsed number value from lexer to node; don't process more than is necessary (a number literal can never be negative, because the negative sign is an Op token and node) * normalize NumberLiteral values * use parsedValue in getNumberValue() * recursive getNumberValue() * parseNumber() * The core JavaScript Number constructor does a better job at parsing strings into numbers than our helper does * Use Object.assign rather than merge or extend * Update link * Cleanup style * Refactor to make AST generation more object-oriented: have each of the AST properties be generated on the node itself, rather than in loops in the base class * Untangle test helpers: give the AST location tests their own specific helper function, and move the general AST helper functions into the main AST tests file * Not passing o * Add node type check to AST location data tests
2018-09-17 17:40:37 +00:00
eq node.loc.start.column, expected.loc.start.column, \
test nested location data
2018-09-17 16:27:30 +00:00
"Expected location start column #{reset}#{node.loc.start.column}#{red} to equal #{reset}#{expected.loc.start.column}#{red}#{pathStr}"
AST generation hooks (#5099) * include range in location data * use exclusive ranges * ast generation hooks * fix getAstChildren() * babylon - * isArray -> Array.isArray * pass options to toJSON() * default astType on Base * using exclusive range * extract location data tests * babylon -> ast * remove do -> * _toAst -> getAstContent * Pass through parsed number value from lexer to node; don't process more than is necessary (a number literal can never be negative, because the negative sign is an Op token and node) * normalize NumberLiteral values * use parsedValue in getNumberValue() * recursive getNumberValue() * parseNumber() * The core JavaScript Number constructor does a better job at parsing strings into numbers than our helper does * Use Object.assign rather than merge or extend * Update link * Cleanup style * Refactor to make AST generation more object-oriented: have each of the AST properties be generated on the node itself, rather than in loops in the base class * Untangle test helpers: give the AST location tests their own specific helper function, and move the general AST helper functions into the main AST tests file * Not passing o * Add node type check to AST location data tests
2018-09-17 17:40:37 +00:00
eq node.loc.end.line, expected.loc.end.line, \
test nested location data
2018-09-17 16:27:30 +00:00
"Expected location end line #{reset}#{node.loc.end.line}#{red} to equal #{reset}#{expected.loc.end.line}#{red}#{pathStr}"
AST generation hooks (#5099) * include range in location data * use exclusive ranges * ast generation hooks * fix getAstChildren() * babylon - * isArray -> Array.isArray * pass options to toJSON() * default astType on Base * using exclusive range * extract location data tests * babylon -> ast * remove do -> * _toAst -> getAstContent * Pass through parsed number value from lexer to node; don't process more than is necessary (a number literal can never be negative, because the negative sign is an Op token and node) * normalize NumberLiteral values * use parsedValue in getNumberValue() * recursive getNumberValue() * parseNumber() * The core JavaScript Number constructor does a better job at parsing strings into numbers than our helper does * Use Object.assign rather than merge or extend * Update link * Cleanup style * Refactor to make AST generation more object-oriented: have each of the AST properties be generated on the node itself, rather than in loops in the base class * Untangle test helpers: give the AST location tests their own specific helper function, and move the general AST helper functions into the main AST tests file * Not passing o * Add node type check to AST location data tests
2018-09-17 17:40:37 +00:00
eq node.loc.end.column, expected.loc.end.column, \
test nested location data
2018-09-17 16:27:30 +00:00
"Expected location end column #{reset}#{node.loc.end.column}#{red} to equal #{reset}#{expected.loc.end.column}#{red}#{pathStr}"
AST generation hooks (#5099) * include range in location data * use exclusive ranges * ast generation hooks * fix getAstChildren() * babylon - * isArray -> Array.isArray * pass options to toJSON() * default astType on Base * using exclusive range * extract location data tests * babylon -> ast * remove do -> * _toAst -> getAstContent * Pass through parsed number value from lexer to node; don't process more than is necessary (a number literal can never be negative, because the negative sign is an Op token and node) * normalize NumberLiteral values * use parsedValue in getNumberValue() * recursive getNumberValue() * parseNumber() * The core JavaScript Number constructor does a better job at parsing strings into numbers than our helper does * Use Object.assign rather than merge or extend * Update link * Cleanup style * Refactor to make AST generation more object-oriented: have each of the AST properties be generated on the node itself, rather than in loops in the base class * Untangle test helpers: give the AST location tests their own specific helper function, and move the general AST helper functions into the main AST tests file * Not passing o * Add node type check to AST location data tests
2018-09-17 17:40:37 +00:00
test "AST location data as expected for NumberLiteral node", ->
testAstLocationData '42',
type: 'NumericLiteral'
start: 0
end: 2
range: [0, 2]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 2
test "AST location data as expected for InfinityLiteral node", ->
testAstLocationData 'Infinity',
type: 'Identifier'
start: 0
end: 8
range: [0, 8]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 8
test "AST location data as expected for NaNLiteral node", ->
testAstLocationData 'NaN',
type: 'Identifier'
start: 0
end: 3
range: [0, 3]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 3
test "AST location data as expected for IdentifierLiteral node", ->
testAstLocationData 'id',
type: 'Identifier'
start: 0
end: 2
range: [0, 2]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 2
test "AST location data as expected for StatementLiteral node", ->
testAstLocationData 'break',
type: 'BreakStatement'
start: 0
end: 5
range: [0, 5]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 5
testAstLocationData 'continue',
type: 'ContinueStatement'
start: 0
end: 8
range: [0, 8]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 8
testAstLocationData 'debugger',
type: 'DebuggerStatement'
start: 0
end: 8
range: [0, 8]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 8
test "AST location data as expected for ThisLiteral node", ->
testAstLocationData 'this',
type: 'ThisExpression'
start: 0
end: 4
range: [0, 4]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 4
test "AST location data as expected for UndefinedLiteral node", ->
testAstLocationData 'undefined',
type: 'Identifier'
start: 0
end: 9
range: [0, 9]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 9
test "AST location data as expected for NullLiteral node", ->
testAstLocationData 'null',
type: 'NullLiteral'
start: 0
end: 4
range: [0, 4]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 4
test "AST location data as expected for BooleanLiteral node", ->
testAstLocationData 'true',
type: 'BooleanLiteral'
start: 0
end: 4
range: [0, 4]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 4
force update location data in grammar
2018-08-24 18:07:17 +00:00
test "AST location data as expected for Access node", ->
use new ast methods
2018-09-17 02:45:11 +00:00
testAstLocationData 'obj.prop',
force update location data in grammar
2018-08-24 18:07:17 +00:00
type: 'MemberExpression'
object:
start: 0
end: 3
range: [0, 3]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 3
property:
start: 4
end: 8
range: [4, 8]
loc:
start:
line: 1
column: 4
end:
line: 1
column: 8
start: 0
end: 8
range: [0, 8]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 8
use new ast methods
2018-09-17 02:45:11 +00:00
testAstLocationData 'a::b',
force update location data in grammar
2018-08-24 18:07:17 +00:00
type: 'MemberExpression'
object:
object:
start: 0
end: 1
range: [0, 1]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 1
property:
start: 1
end: 3
range: [1, 3]
loc:
start:
line: 1
column: 1
end:
line: 1
column: 3
property:
start: 3
end: 4
range: [3, 4]
loc:
start:
line: 1
column: 3
end:
line: 1
column: 4
start: 0
end: 4
range: [0, 4]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 4
use new ast methods
2018-09-17 02:45:11 +00:00
testAstLocationData '''
test parens
2018-08-24 19:49:19 +00:00
(
obj
).prop
''',
type: 'MemberExpression'
object:
start: 4
end: 7
range: [4, 7]
loc:
start:
line: 2
column: 2
end:
line: 2
column: 5
property:
start: 10
end: 14
range: [10, 14]
loc:
start:
line: 3
column: 2
end:
line: 3
column: 6
start: 0
end: 14
range: [0, 14]
loc:
start:
line: 1
column: 0
end:
line: 3
column: 6
force update location data in grammar
2018-08-24 18:07:17 +00:00
test "AST location data as expected for Index node", ->
use new ast methods
2018-09-17 02:45:11 +00:00
testAstLocationData 'a[b]',
force update location data in grammar
2018-08-24 18:07:17 +00:00
type: 'MemberExpression'
object:
start: 0
end: 1
range: [0, 1]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 1
property:
start: 2
end: 3
range: [2, 3]
loc:
start:
line: 1
column: 2
end:
line: 1
column: 3
start: 0
end: 4
range: [0, 4]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 4
use new ast methods
2018-09-17 02:45:11 +00:00
testAstLocationData 'a?[b][3]',
force update location data in grammar
2018-08-24 18:07:17 +00:00
type: 'MemberExpression'
object:
object:
start: 0
end: 1
range: [0, 1]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 1
property:
start: 3
end: 4
range: [3, 4]
loc:
start:
line: 1
column: 3
end:
line: 1
column: 4
start: 0
end: 5
range: [0, 5]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 5
property:
start: 6
end: 7
range: [6, 7]
loc:
start:
line: 1
column: 6
end:
line: 1
column: 7
start: 0
end: 8
range: [0, 8]
loc:
start:
line: 1
column: 0
end:
line: 1
column: 8