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
loadProject() should always return a project api, with any errors in project.errors. Since this is hard to guarantee, errors thrown by loadProject() are already partly handled in sherlock. but there are still several code paths which assume that state().project is not undefined.
e.g. here and here and bug here
Proposal
It would be nice for users to be able to select "no project" e.g. if they are working on a non-i18n package in a monorepo, and don't want to pay for sherlock resource consumption.
The option would also be helpful to disable the default project message loading for repos with one really big project (1000's of messages) which (currently) slows down vs code and probably results in users uninstalling sherlock.
The text was updated successfully, but these errors were encountered:
You are right 👍 With the introduction of the project tab, there is the case of "No project could can be found" and therefore we should also handle this explicitly in the extension.
Context
loadProject()
should always return aproject
api, with any errors in project.errors. Since this is hard to guarantee, errors thrown by loadProject() are already partly handled in sherlock. but there are still several code paths which assume that state().project is not undefined.e.g. here and here and bug here
Proposal
It would be nice for users to be able to select "no project" e.g. if they are working on a non-i18n package in a monorepo, and don't want to pay for sherlock resource consumption.
The option would also be helpful to disable the default project message loading for repos with one really big project (1000's of messages) which (currently) slows down vs code and probably results in users uninstalling sherlock.
The text was updated successfully, but these errors were encountered: