Inconsistent type mixin and atrule for SCSS parser

[lmeysel]

Hi, i came accross an inconsitency while parsing SCSS.

To reproduce:

import gonzales from 'gonzales-pe';
const tree = gonzales.parse('@mixin foo() {}\n@function bar() {}', { syntax: 'scss' });

This example produces the following output (I removed the unnecessary information). The mixin produces a node with type mixin whereas the function produces an atrule containing a function.

Imho the mixin should also produce an atrule containing a mixin.

{
  "type": "stylesheet",
  "content": [
    {
      "type": "mixin", // <--- top-level mixin
      "content": [
        {
          "type": "atkeyword",
          "content": [
            {
              "type": "ident",
              "content": "mixin",
            }
          ],
        },
        {
          "type": "ident",
          "content": "foo",
        },
       // ...
      ]
    },
    {
      "type": "atrule",  // <--- top-level atrule
      "content": [
        {
          "type": "atkeyword",
          "content": [
            {
              "type": "ident",
              "content": "function",
            }
          ],
        },
        {
          "type": "function", // <--- ... containing a function
          "content": [
            {
              "type": "ident",
              "content": "bar",
            },
          ],
        },
        // ...
      ],
    }
  ],
}

[lmeysel]

Not sure whether this should be a new issue, but another inconsitency occurs when parsing @each and @for loops.
While @for is wrapped in a loop/atkeyword/ident=for, whereas @each is atrule/atkeyword/ident=each