Fix: Format model on save

[mykalmax]

No description provided.

[vchan]

What about formatting content instead of the file? Also, do we want to format when renaming a file? Users might not expect that.

[vchan]

Settings wouldn't have changed, right?

Suggested change

	path_or_new_path_mapping = await get_path_mapping(settings=get_settings())
	path_or_new_path_mapping = await get_path_mapping(settings=settings)

[mykalmax]

@vchan
In general i would expect some formatting on save. But in our case formatting models not just fix indentation.
Before:

After:

[vchan]

Should we use the model's dialect if it has a non-default dialect?

[vchan]

What happens if the file isn't a sql file?

[vchan]

Looking at the source code and docstring for parse(), default_dialect should be the project wide config dialect.

[vchan]

If the formatting fails, should we still write the original content?

[vchan]

Maybe we can update get_path_mapping to map paths to models and use it here instead of searching through all models every time user saves.

[mykalmax]

we're using get_path_mapping not just for models but for files in general

[vchan]

Why is this removed? Is it because the file watcher reloads the context on file changes now?

[mykalmax]

yes, file watcher reloads the context on model or seed file changes and collecting models to send over SSE

[vchan]

This can be removed or replaced with a SSE message warning the file couldn't be formatted. What do you think?

[vchan]

Lines 75-78 can all go into this if block.