`no-identical-title` maybe could be ignored for nested `describe` blocks...?

My scenario is that the linter is whining about no-identical-titles for nested describes where that nested title is actually what i want.

Imagine this:

describe("my component", () => {
  describe("west facing", () = {
    describe("when the sun is up", () => {  
       it("sees the sun", () => {});
    })
    describe("when the sun is down", () => {  
       it("sees the moon", () => {});
    });
  });
  describe("east facing", () = {
    describe("when the sun is up", () => {  
       it("does not see the sun", () => {});
    })
    describe("when the sun is down", () => {  
       it("sees whatever", () => {});
    });
  });
});

In this case… the linter doesn’t like when the sun is up and when the sun is down because they are the same, but as nested describes, they seem like a valid use case.

What do you think of that? could there be a rule that looks at the full “nested” title to determine it’s allowed “uniqueness”?

[SimenB]

That definitely makes sense! We should try to match against full names (so my component > west facing > when the sun is up > sees the sun) and not against describes and its in isolation.

Not sure how hard that is, but PR welcome!

[bunnymatic]

Fine with me!