"Code info" panel does not update Document frequency value if left open

[stragu]

Steps to reproduce:

1. Have a document and several codes ready
2. Open Annotate tab
3. Expand a "Code info" panel underneath a code by clicking the three-dot menu
4. Select bits of text and use that code on them

Result: the value for "Document frequency" does not change.

Expected: the value updates as we code more sections.

Workaround: close and reopen the "Code info" panel to update the value.

Using the https://requal.fsv.cuni.cz/demo/ demo instance, which reports to use version 1.2.4.9001.

[martin-hajek]

I can confirm that this issue occurs in versions 1.1.3.9001 and higher (desktop version). When I created a new project with a document, added two codes and labelled some segments with them, the coded segments did not appear in either the Analyse tab (No coded segments detected.) or the Report tab (No segments were coded by selected coders.)

[hlageek]

Thanks for pointing that out. I initially thought it wasn't a big deal, but since the code info panel now includes more features—making it more likely for users to keep it open beyond just checking code frequencies—it's clear that adding reactivity for the frequencies is expected.

[hlageek]

I can confirm that this issue occurs in versions 1.1.3.9001 and higher (desktop version). When I created a new project with a document, added two codes and labelled some segments with them, the coded segments did not appear in either the Analyse tab (No coded segments detected.) or the Report tab (No segments were coded by selected coders.)

This sounds unrelated to the OP. Probably another report of #163. The problem is that I cannot reproduce this behavior.

[martin-hajek]

I can confirm that this issue occurs in versions 1.1.3.9001 and higher (desktop version). When I created a new project with a document, added two codes and labelled some segments with them, the coded segments did not appear in either the Analyse tab (No coded segments detected.) or the Report tab (No segments were coded by selected coders.)

This sounds unrelated to the OP. Probably another report of #163. The problem is that I cannot reproduce this behavior.

You are right, I confused two things. Anyway, my issue disappeared after I force reinstalled requal, which updated also the 'later' package.

[hlageek]

Potential enhancement for testing is deployed on https://requal.fsv.cuni.cz/demo/

[stragu]

Works fine, thank you! Only issue is how jumpy / flickery it is. But I think it's better than not updating the value.

[hlageek]

Thanks for checking @stragu. I do not experience any flickering when running Requal locally, but I too have noticed it on the demo (though not entirely consistently). I suspect that a delay between the server and the browser may have something to do with it. Refactoring the update from Shiny into JavaScript could possibly help, but as long as the functionality works as expected, I also see the effort to reduce flickering as a low-priority new issue.

[stragu]

sounds great, thanks so much @hlageek :)

[hlageek]

Closing this via #174, may take a second look at the flickering artifact during future work on "Code info" panel features.