Sameera Jayasoma

That's precisely the proposal, Sanjiva. I guess the original description wasn't clear. > - Any direct subdirectory becomes a module in the package. > - Those subdirectories will logically merge...

There can be VSCode code actions that update the generated code. E.g., we plan to have code actions to generate or update the generated code for changes in entity definitions....

This capability is available in Ballerina now.

Relates to #101

I propose going ahead with the `@embed` approach here. It's similar to C #embed and Go //embed. @jclark I didn't quite understand your point about the `@embed` annotation.

Here are the proposed semantics of the `@embed` annotation: - It can only be attached to module-level variables of type `string` or `readonly & byte[].` - The given pattern should...

Compiler plugins (analyzers) enforce constraints on packages. Here are some sample constraints: - No service declarations are allowed - No Listeners are allowed - All public functions must be expression-bodied...

As per this [comment](https://github.com/ballerina-platform/ballerina-spec/issues/1114#issuecomment-1163629120), compiler plugins, especially code analyzers, enforce constraints on the Ballerina package. Therefore without introducing a new concept here, can we use compiler plugins to achieve the...

We agreed to go ahead with the proposal in this [comment](https://github.com/ballerina-platform/ballerina-spec/issues/1114#issuecomment-1270760416).

There is no standard way to specify environment variables in `.toml` files. See: https://github.com/toml-lang/toml/issues/25