namespacing | Clojure like namespaces for Ruby | Code Inspection library

It's actually a bit strange to call them "nested libraries" since you want to call them with Lib.Utils.Whatever. Utils, here, is a sub-module of Lib. Here's what I was able to do if it can help you:

I'll leave an answer because this won't fit inside a comment.

As I understand you deploy some kind of software development kit for lib1 and lib2. Each SDK contains some public headers and the lib1 and lib2 static libs. Both of these libraries are statically linked with lib3, which is an internal library.

So the SDKs could look something like this:

I'm not sure what this monkeypatch is really supposed to accomplish. But one way of avoiding the error is by not using ActiveSupport::Concern#included. Instead just use the actual Ruby hook (Module#included) that it abstracts away:

It turned out, that my local webserver (Apache2) used a different PHP-CLI than my development environment and therefore all the enabled extensions and configurations had no effect as soon as the request got parsed to the webserver.

Use docker kids.

In your user/mutations.js file you use the getDefaultState()-function, but you need to import it in order for the mutations to know what it is. In order to import it, you also have to export it.

So your user/state.js should be changed to this:

Your stack trace is pretty straightforward. It's telling you:

1. You haven't successfully required your Scraper class/module.
2. There's no CLI::Scraper defined in your current namespace.
3. You're invoking methods on objects that aren't in scope or that don't exist in your code at all.

Address the issues above, and see where that gets you. Off the cuff, there a few concrete things you should consider as you debug your program:

1. Your CLI class has no way to reference a Scraper class/module outside its namespace unless you tell it where to look through importing modules or namespacing them within a common module so you can reference Foo::Scraper and Foo::CLI explicitly.

2. Your probably better off injecting a Scraper into your CLI initialization anyway, but you haven't shown enough code to offer a meaningful example.

3. Strip away all non-essential code until you can get the basics working. For example:

• Yes, trees (and even DAG) structures are fully supported. The type definition is recursive, but the data will eventually have leaf nodes with an empty vector of children, presumably.
• The integer value for V1 is 0, and that is also the default value for all fields with no explicit default assigned. Use --defaults-json to see this field when converting. Note that explicit versions in a schema is an anti-pattern, since schemas are naturally evolvable without breaking backwards compatibility.
• You can put enum fields in structs, yes. Is that what you mean?

Yes, you either have to prefix the function with its namespace (use the fully qualified name of it) or alias the function before calling it using the use statement (usually right after the namespace declaration - if any - or at the beginning of the file otherwise).

This seems to be a problem with the virtual box filesystem. I created an issue to composer and hopefully more insight will be gained.

https://github.com/composer/package-versions-deprecated/issues/21