> For the complete documentation index, see [llms.txt](https://clapy.gitbook.io/clapy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clapy.gitbook.io/clapy/extras/changelog/25-07-2022.md).

# 25/07/2022

Here is what changed this week on Clapy.

### Breaking changes

* To generate the code for a page and stretch to the whole page, you need to check the new option: "**Full width/height**".\
  Previously, it was assumed from the layout of the parent element, but was undesired in some cases.

### New features

* New option: [Full width/height](https://docs.clapy.co/#full-width-height).
* New option: [SCSS (experimental)](https://docs.clapy.co/#scss-instead-of-css-beta). It generates SCSS files instead of CSS. As of now, only the extension changes with this option. Please let us know for more changes!
* New option: [SCSS > BEM conventions](https://docs.clapy.co/#scss-instead-of-css-beta). It indents class names in SCSS files.
* Generate code when a *Component Set* is selected in Figma. All components in the *Component Set* are generated as if it was a *Frame*.

### Bug fixes

* The layout of SVG elements have been fixed in specific cases

{% hint style="info" %}
Any feature you would love to find in Clapy? [Happy to discuss it](https://clapy.co/contact)!
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://clapy.gitbook.io/clapy/extras/changelog/25-07-2022.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.