« get me outta code hell

data: always define composite utilities with `key() {}` syntax - hsmusic-wiki - HSMusic - static wiki software cataloguing collaborative creation
about summary refs log tree commit diff
path: root/tap-snapshots/test/snapshot/generateAlbumTrackList.js.test.cjs
diff options
context:
space:
mode:
author(quasar) nebula <qznebula@protonmail.com>2023-08-30 16:28:47 -0300
committer(quasar) nebula <qznebula@protonmail.com>2023-09-05 21:02:54 -0300
commit011c197aeedab56d501b03b800433dd0cd9bc4f7 (patch)
tree86c24338c20fc92fdb5dfcbb2f0eb335993f6a01 /tap-snapshots/test/snapshot/generateAlbumTrackList.js.test.cjs
parent7d6d8a2839ece38c4a70bd9e3fda73b2e0aa39b8 (diff)
data: always define composite utilities with `key() {}` syntax
Sublime Text doesn't index the key in `key: () => {}` as a symbol
for function definitions if the parameter list takes up more than
one line, but always works for `key() {}`.

This also just makes it a little easier to add "preamble" before
the main return value, when relevant. Consistent syntax is usually
a plus for recurring behavioral forms!
Diffstat (limited to 'tap-snapshots/test/snapshot/generateAlbumTrackList.js.test.cjs')
0 files changed, 0 insertions, 0 deletions