mirror of
				https://github.com/mozilla/gecko-dev.git
				synced 2025-10-31 16:28:05 +02:00 
			
		
		
		
	|  6ed63d3402 This one extends on the last change. We now generate the base class for trait/callback interfaces that can be defined in JS and require implementations to extend that class. It seems reasonable and would make the code that joschmidt wrote work without issues. However, I'm not totally sure about it is more or less idiomatic to create these class hierarchies? Also: removed the `self_name` field, which wasn't used. Differential Revision: https://phabricator.services.mozilla.com/D255321 | ||
|---|---|---|
| .. | ||
| components | ||
| src | ||
| test-fixtures | ||
| tests | ||
| uniffi_bindings_tests | ||
| uniffi_bindings_tests_collision | ||
| uniffi_bindings_tests_external_types | ||
| askama.toml | ||
| Cargo.toml | ||
| config.toml | ||
| mach_commands.py | ||
| README.md | ||
This directory contains crates that bundle UniFFI-enabled components together. This enables uniffi-bindgen-gecko-js to build the components into a shared lib and generate the bindings using library mode.