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.
@gruehle and I both recently had our indent size setting suddenly change to 1 (from our usual 4) with no warning. We're not sure why.
@zoufahl noted that his CSS code hinting unit tests manually set it to 1. Looking at the unit test code, they're definitely doing it in a way that could break other unit tests -- the setting is changed as soon as the test module loads (even if it's never run), and it's never reset later. But it doesn't readily affect the main Brackets window, even if I explicitly run the test.
It's likely the cause anyway, but I'm just not sure how (and/or what circumstances will make it repro).
If it's the unit test though, this luckily won't affect installer builds, since those exclude all unit test code.
The text was updated successfully, but these errors were encountered:
I think for now this piece of code can be removed.
I initially put it there to simulate users pressing 'Tab' without changing my testdocuments (and also I didn't wanted to guess the users indent size).
Since this feature isn't used at all in the unittests so far, it's save to remove it (for now).
I don't really have a means to verify since Glenn and I each only hit this once and weren't able to repro it. Closing, and I'll just reopen if anyone sees this again.
@gruehle and I both recently had our indent size setting suddenly change to 1 (from our usual 4) with no warning. We're not sure why.
@zoufahl noted that his CSS code hinting unit tests manually set it to 1. Looking at the unit test code, they're definitely doing it in a way that could break other unit tests -- the setting is changed as soon as the test module loads (even if it's never run), and it's never reset later. But it doesn't readily affect the main Brackets window, even if I explicitly run the test.
It's likely the cause anyway, but I'm just not sure how (and/or what circumstances will make it repro).
If it's the unit test though, this luckily won't affect installer builds, since those exclude all unit test code.
The text was updated successfully, but these errors were encountered: