-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repository button disappears on 5.1.4 (regression from 5.1.3) #197
Comments
I assume what has happened is the config has changed the defaults for some reason or another. This is fully configurable tho see #183 for full config Nothing logically should have changed regarding anything to do with the presence the only changes in 5.1.3 and 5.1.4 was adding debug to the buttons. |
Dont know what to tell you. Matter of fact is that the first button is VERY broken on 5.1.4. Maybe the wrong files were pushed to the market place and what is on there does not reflect the source code on here. Either way, on 5.1.4 the first button completely ignores the git repository, while 5.1.3 works flawlessly in that regard. I just tried again to confirm, and used the same hardcoded custom settings just to be sure, issue persists. |
What is the state that is left out I don't think we want to return inactive if the state is actually undefined. State should not be undefined either if the state shouldn't be shown due to an exemption or something else that has gone wrong. If state is undefined we are missing a case in the switch statement and that should be fixed. Also this causes issues in git repos if it is undefined because git doesn't have a inactive state Once I flush out all the issues with the switching I would like to move this way of doing things to other areas were code has been repeated over and over again. So it is important that we accommodate this and handle the outcome that we are missing. If I can find a clean nice way of doing it. Can u post the config you have set I do not have a problem with what you are describing / cant recreate it in the live version? Also steps to reproduce. In git/not in git. idle etc This is my exact config for buttons
In git repo no file In git idle state: In FIle Idle state in file Idle state not in file (this issue with the :: and no file name has been in vscord for ages. I have seen it a few times makes sense why it is happening with not being in a file) Also this shouldn't be undefined. I think it will break the ignore repo / workspace / org checks. As if it is gitExluded it uses the inactive status I am pretty sure. I would have to actually test and look into it tho |
I have an issue on 5.1.4, which is not present on 5.1.3.
On 5.1.3, with the default configuration, the first "View Repository" button is shown when a repo is detected, and remains shown when idle or when not in a file. On 5.1.4 instead I've had many issues with this behavior, like the button disappearing when idle or not in a file, or the link being incorrect and pointing to a rick roll, and if I manually override the rick roll link, it fails to parse the
{git_url}
and says invalid URL for button 1. I would assume this is due to a logic mistake, where the git repo context is skipped if idle state is detected.I'm also having another logic issue, which is kind of expected and behaving correctly, but makes little sense. I included file details like filename and line count in the state text (second line) to also show when idle, and set the not in file text correctly.When I go idle on a file, I keep seeing the correct details, and if I'm not in a file that also shows correctly; going idle when not in a file however, will try to use the idle text instead of the not in a file text, which is correct logic wise, but this means that the file information string is used and leaves details empty (in my case I see
( lines)
due to missing filename and line count). I see 2 possible solutions: using the "not in file" text when "idle and not in file", or adding an additional config entry for "idle and not in file" state.The text was updated successfully, but these errors were encountered: