GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Rename `fresh` to more useful name · Issue #373 · liquid-java/liquidjava

Rename fresh to more useful name #373

New issue
Copy link
New issue
Copy link
Closed
#477
Closed
Rename fresh to more useful name#373
#477
Copy link
Labels
enhancementNew feature or requestNew feature or requeststudyNeeded before the error-message user studyNeeded before the error-message user study

Description

@CatarinaGamboa
CatarinaGamboa
opened on Oct 8, 2026
Issue body actions

Problem
When we add a path condition, the variable getting that result is called freshX.
That works internally but it doesn't resonate a lot for a developer to understand thats a path condition.
We can use better names like then_branch or then, or similar ones, to clearly identify what the variable represents.

In the example below we can change the fresh to one of those solutions

Image

Activity

  1. CatarinaGamboa
    added
    enhancementNew feature or requestNew feature or request
    on Oct 8, 2026
  2. CatarinaGamboa
    changed the title [-]Change fresh to then in path if[/-] [+]Rename `fresh` to more useful name[/+] on Oct 8, 2026
  3. CatarinaGamboa commented on Nov 2, 2026

    @CatarinaGamboa
    CatarinaGamboa
    on Nov 2, 2026
    CollaboratorAuthor
    More actions

    The same names show up in the error-message study exercises, where they are most of what Found shows: JabRef's EditAction has #fresh⁸³⁸, #fresh⁸³⁹, #fresh⁸⁵¹, #fresh⁸⁵² and #fresh⁸⁵³ for the if/switch conditions above the call (example in #375). In OpenNMS's probe, the counterexample is #fresh¹²⁵⁶ == false, which a reader can't map back to a line of code (see also #453).

  4. CatarinaGamboa
    added
    studyNeeded before the error-message user studyNeeded before the error-message user study
    on Nov 2, 2026
  5. CatarinaGamboa
    added 3 commits that reference this issue on Nov 3, 2026

    Drop true binders the error does not need and write fields as in code (…

    70edf72

    Drop true rows for variables that another row of Found already shows (#…

    926f027

    Drop the bare true row left at the end of Found (#476)

    c974821
  6. CatarinaGamboa
    closed this as completedin cd49feaon Nov 4, 2026
  7. CatarinaGamboa
    added 2 commits that reference this issue on Nov 4, 2026

    Name generated values after what they are instead of #fresh

    This issue will close once commit a4a38c4 is merged into the 'main' branch.
    a4a38c4

    Name refined call results after the method, as the other generated va…

    This issue will close once commit 03b2d8b is merged into the 'main' branch.
    03b2d8b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestNew feature or requeststudyNeeded before the error-message user studyNeeded before the error-message user study

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402520 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.