wasify-io / wasify-go Goto Github PK

Allow file system configuration functionality in ModuleConfig

FSConfig: wasify.FSConfig{
	Enabled:  true,
	HostDir:  "./dir",
	GuestDir: "/",
}

Add tests that tests wazero specific code and validates WASM/module behaviours.

Simplify return values from guest functions.

Considering this project isn't maintained, at least notify potential users about it.

Add log host function to allow guest users to log and debug their modules using mdk

mdk.Log()

depends on #2

Add optional Attributes field for ModuleConfig

type ModuleConfig struct {
	...
	Attributes    map[string]string
	....
}

These attributes will be accessible within the module with the help of Module Development Kit mdk.

val := mdk.Attr("key") // val or nil
//  Or mdk.GetAttr("key") ? 

optionally, good to have built-in converters:

val := mdk.Attr("name").String()
val := mdk.Attr("age").Int()
...

Error wrapping is a beneficial practice in Go's public APIs because it enhances clarity and problem-solving for users. By adding context to error messages, developers can quickly understand why an error occurred and trace its origins. This makes troubleshooting and resolution more efficient, shields internal implementation details, and maintains consistency in error handling. Moreover, it aids in versioning and ensures that changes to underlying code don't disrupt users' error-handling strategies.

Add missing unit tests.

In wasm runtimes, basic functions like serving web pages or logging data aren't included by default. For example, if we want to send a request to a website from a part of our wasm program, we first need to set up a special host function for this purpose. Then, we can use that function within the module to get the data we need. It's a good idea to prepare essential functions like these in advance for users.

We should create a feature that makes it easy to generate these built-in functions, which can be used by people who write wasm programs. This way, users can perform tasks like making web requests without the hassle of setting up everything from scratch. The goal is to simplify the process for everyone involved.

Supported types in Params and Results are only "byte" right now. []byte is simple and useful. However, it would be nice to also have number types like uint32, uint64, float32, and float64.