Will Demaine

I've figured out a kind of workaround. You can use route groups `(group)` to 'mirror' what would be a nested route, e.g: ``` app ├── (app) │   ├── (leaves) │  ...

For anyone looking for a workaround for this, we are now doing: ``` type ErrorReasoner interface { ErrorData() interface{} } // extractErrorMessage extract the error message in a failed transaction...

Hey @juanfranblanco would love to get your thoughts on this. It currently works as is but it's quite a large change so would like to get any feedback before doing...

I am more than happy to rework all of this if needed. I've been using it for my own projects, and just decided to clean it up and try and...

Sounds good! So then I would propose that we have: ``` solidity.developmentEnvironment: [forge, hardhat] // as a dropdown with just these values (for now). ``` And the existing: ``` solidity.test.command...

If it makes sense, I'll probably do the environment + detection part as a separate PR, and then follow with this one to try and keep the size down a...

Hey, I'm happy to fix things up if needed. Not quite sure what you mean about getting mixed with the environment? In terms of the command execution, I wasn't really...

Hey @daumann, I think that putting everything in the store is necessary. The lat/long determines the centre point for rendering. If you remove it, I think the map will rubberband...

``` error eslint 26:12 Strings must use singlequote. quotes error jscs 26:12 Invalid quote mark found validateQuoteMarks ```