MariusDrulea

potential issue: 5 commits from my previous PR still appear here; they were merged into Makie/master as a unified commit; after merging Makie/master back into MariusDrulea/Makie/master, these individual commits still...

**Edit:** While writing a more detailed example, I realized DataInspector is pretty much correct. The issue is that I have to pass `x'` as input and therefore `img[20, 1] =...

At the end I think we shall edit the default behaviour for images and heatmaps. We shall only call `image(x)` and get the expected behavior. So no more transposition, no...

**Side info: how @from works?** For each `@from "my_file" using mymod` a module `Main.absolute_path_to_my_file.mymod` is created globally. Any new @from of the same file will simply take the definition from...

I think it does not hurt to have the feature. @from has a specific format that we can clearly match in the StaticLint. It looks like there is no danger...

here is my PR for StaticLint: https://github.com/julia-vscode/StaticLint.jl/pull/319

@Shuenhoy I also like the idea of this plugin mechanism. The only thing I added is a `function resolve_FromFile_import(x::EXPR, state::State)`. The first lines of code of this functions checks if...

Isn't ok to have "scripted" plugins for now, instead of declarative plugins? I understand declarative plugins is a better design choice, but does it really hurt to have those "scripted"...

The `StaticLint` has the following top level function, see the code bellow. `x` is a CSTParser expression, which is similar to a julia metaprogramming expression. Let's take this ```resolve_FromFile_import(x, state)```....

@davidanthoff I like your proposal and it looks quite feasible to do that. I might have a simpler solution. I'm thinking to avoid managing the abstract syntax tree, if possible....