You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
Result:
Console contains error "addMenuItem() -- error: 3 when adding command: bracketless.enabled" indicating an error code returned from brackets.app.addMenuItem().
Expected:
BracketLESS is doing something wrong here: passing a nonexistent command id as the relativeID arg. However, before the native menu migration we gave much more informative error strings. In this case it would have been "_getRelativeMenuItem(): MenuItem with Command id menu-view-sidebar not found in Menu view-menu". The message we actually show is uninformative and almost looks like brackets-shell bug rather then a problem with the extension's code.
The text was updated successfully, but these errors were encountered:
Reviewed. Low priority to @gruehle. Glenn, do you think this could be a starter bug? Could it be fixed purely on the JS side by mapping the error codes to strings, or is there more info we'd need to get from the native side in order to provide good errors?
Result:
Console contains error "addMenuItem() -- error: 3 when adding command: bracketless.enabled" indicating an error code returned from brackets.app.addMenuItem().
Expected:
BracketLESS is doing something wrong here: passing a nonexistent command id as the relativeID arg. However, before the native menu migration we gave much more informative error strings. In this case it would have been "_getRelativeMenuItem(): MenuItem with Command id menu-view-sidebar not found in Menu view-menu". The message we actually show is uninformative and almost looks like brackets-shell bug rather then a problem with the extension's code.
The text was updated successfully, but these errors were encountered: