Harmonize function and trigger names in specs - #208
Open
teoljungberg wants to merge 2 commits into
Open
Conversation
teoljungberg
force-pushed
the
tl-harmonize-test-names
branch
from
March 8, 2026 13:40
436ce3d to
2a9d491
Compare
Use a consistent set of names across the entire test suite: - Functions: value (simple), add (two-arg), make_incr (dependent) - Triggers: set_upper_name, set_lower_name - Table: users with name, upper_name, lower_name This replaces the ad-hoc names (test, adder, greetings, uppercase_users_name, my_function, etc.) that varied across spec files.
teoljungberg
force-pushed
the
tl-harmonize-test-names
branch
from
March 9, 2026 10:10
2a9d491 to
166e65a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
value(simple),add(two-arg),make_incr(dependent)
set_upper_name,set_lower_nameuserswithname,upper_name,lower_nametest,adder,greetings,uppercase_users_name,my_function, etc.) that variedacross spec files