ranfdev

Just to be clear about what i want to build: - I have a website (made with zola, which is awesome btw). - I want to create a section "read...

I was thinking of {% include_raw "file.html" %} file.html is located at include_raw/file.html

> @ranfdev I think for openring Zola's [load_data](https://www.getzola.org/documentation/templates/overview/#load-data) filter could be used actually. That's it! It does what i need, thank you!

The user could still mistype the target property string though. So this doesn't fully solve the underlying problem.

We could introduce a ```rust struct PropertyProxy PropertyProxy(this: Self, target: PropertyProxy

IMHO this is not an idiomatic way to handle the problem. We are polluting the library with a lot of combinations `do_x`, `do_x_with_priority` `do_x_local`, `do_x_with_priority_local`... The same problems exists for...

I would keep the functions #1201 under the futures scope, eg: `glib::futures::spawn_local`. Only because spawn_local is used 10x more than spawn_local_with_priority, so I think it's nice having a shorthand for...

Ah, I didn't expect that. Can we make every `spawn_local` use the priority `default_idle` by default then? For sure I've spawned many futures with `spawn_local` in the past, without thinking...

I agree it's needed, I'm just not convinced about the API. In the meantime it can be implemented by the user using a custom macro `set_if_changed!` ```rust #[properties(get, set =...

There you go, it should cover 99% of the gtk use cases. ```rust macro_rules! set_if_changed { ($ident:ident) => { |this: &&Self, val| { if glib::PropertyGet::get(&this.$ident, |old_val| old_val == &val) {...