Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

Indent/tab size sporadically reset to 1 - due to unit test? #2612

Closed
peterflynn opened this issue Jan 19, 2013 · 5 comments
Closed

Indent/tab size sporadically reset to 1 - due to unit test? #2612

peterflynn opened this issue Jan 19, 2013 · 5 comments
Assignees
Milestone

Comments

@peterflynn
Copy link
Member

@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.

@zoufahl
Copy link

zoufahl commented Jan 19, 2013

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).

@ghost ghost assigned dangoor Jan 28, 2013
@njx
Copy link
Contributor

njx commented Jan 28, 2013

Reviewed. To @dangoor for Sprint 20.

dangoor added a commit that referenced this issue Jan 29, 2013
This is a likely fix for #2612. I was unable to reproduce
that issue, but it is true that this code was no longer needed.
@RaymondLim
Copy link
Contributor

FBNC to @peterflynn

@peterflynn
Copy link
Member Author

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.

@njx
Copy link
Contributor

njx commented Jan 30, 2013

I also hit it once. Will reopen if I see it again, but it's hard to imagine it would happen again after @dangoor's fix.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants