Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 31 2020 18:42
    juanfranblanco commented #196
  • Oct 31 2020 16:34
    deluca-mike commented #196
  • Oct 27 2020 19:31
    wighawag commented #190
  • Oct 21 2020 02:44
    deluca-mike commented #160
  • Oct 21 2020 02:43
    deluca-mike commented #160
  • Oct 21 2020 02:43
    deluca-mike commented #160
  • Oct 21 2020 02:37
    deluca-mike commented #149
  • Oct 20 2020 08:06
    thbourlove opened #199
  • Oct 16 2020 07:00
    juanfranblanco closed #195
  • Oct 16 2020 07:00
    juanfranblanco commented #195
  • Oct 13 2020 21:05
    arkeo01 opened #197
  • Oct 13 2020 09:21
    juanfranblanco commented #196
  • Oct 13 2020 07:03
    deluca-mike opened #196
  • Oct 09 2020 03:38
    zhengger edited #195
  • Oct 09 2020 03:37
    zhengger opened #195
  • Oct 05 2020 15:12
    juanfranblanco commented #194
  • Oct 05 2020 15:04
    orbs163 edited #194
  • Oct 05 2020 15:03
    orbs163 edited #194
  • Oct 05 2020 15:01
    orbs163 opened #194
  • Oct 05 2020 09:47
    deluca-mike edited #192
Juan Blanco
@juanfranblanco
Remy Willems
@keyboardDrummer
And, regarding the YAKINDU language server, from its page it's not really clear whether it supports LSP. It's not mentioned anywhere. Have you looked into it?
Juan Blanco
@juanfranblanco
yes as it does, mainly they started with Eclipse and move to other IDEs using LSP
so that is great, although I have not seen support for multiple smart contract inheritance and navigation
which is the key part for solidity
Remy Willems
@keyboardDrummer
alright :)
drpeck
@thecircleoflifefree
Hi Team quick question, is there a way to get an ABI json like output as in remix.ide from the vsc ?
So for example i put my contract, then con the compile tab at the bottom there is a ABI and BYTECODE button
An output like this would be given:
                  "constant": false,
                  "inputs": [
                      {
                          "name": "_name",
                          "type": "string"
                      },
                      {
                          "name": "_age",
                          "type": "uint256"
                      }
                  ],
cheers!
Juan Blanco
@juanfranblanco
@thecircleoflifefree just compile your contract in VSCode
the abi can be found in the bin folder
Yaom!ng
@FrameVolt
Does vscode-solidity extension good support with unity3d?
Yaom!ng
@FrameVolt
because I got few error with generated service code. And I think those code not needed in unity3d. does anyway not generate those code?
Juan Blanco
@juanfranblanco
@FrameVolt for Unity3d you don't need to use the service code if working with coroutines
Just delete the service
Yaom!ng
@FrameVolt
thank you
Yaom!ng
@FrameVolt
Question, On solidity overload function, after generate, will get same class name, how to avoid this happen?
Juan Blanco
@juanfranblanco
I have not fixed that yet for code generation.. the simple best option is to have 2 different method names
The plan is to name the classes with a number suffix, which also is not very descriptive
Elena Gesheva
@elenadimitrova
@juanfranblanco I am thinking of potentially extending the console "problems" tab to be able to group solc (and lint) errors and warning there by type and not just filename.
I originally wrote up the problem to the solidity team here ethereum/solidity#9002 but after Chris responded I realised it's better added to a dev ide
Any initial thoughts are appreciated
Juan Blanco
@juanfranblanco
hi @elenadimitrova how are you? that is a good idea. Althought I don't know if vscode supports that type of grouping..
Elena Gesheva
@elenadimitrova
Hey @juanfranblanco :wave: I’m fine thanks :) Just bumping into issues when doing large repo-wide contract upgrades as the tooling is still bare minimum, not that I’m complaining :)
But you’re right microsoft/vscode#41114
I’ll reopen that discussion as I think they prematurely closed it and it has been 2 years..
Elena Gesheva
@elenadimitrova
Juan Blanco
@juanfranblanco
@elenadimitrova Nice!! I think a simple sorting order based on issue description will help everyone using vscode
Pylyp Radionov
@rad-p
does go to definition works?! I can't use it ;( says 'No definition found'
have
vsc: 1.47.1
os: linux x64 5.4.0-40-generic
chrome: 78.0.3904.130
node.js : 12.8.1
Juan Blanco
@juanfranblanco
@rad-p you many need to post a sample
oppenheim
@oppenheim

Go to definition does not work for me as well. I tried to understand why, and found out that a few of the newer keywords in solidity (mostly 0.6+) are causing the parser to fail:

  1. receive() functions
  2. call{value:, gas:} syntax
  3. Abstract contracts
  4. Variable override (function override is fine)
  5. Interface contracts
  6. fallback() functions

Removing those keywords from the project solved the problem for me.

Juan Blanco
@juanfranblanco
hi yes solparse as it is old won't recognise those as keywords
the idea is to move now to antlr and refactor that
but i will investigate for an intermidiate solution
as it will take some time :)
Si
@firevenus
hi
Juan Blanco
@juanfranblanco
Hi
Si
@firevenus
is it ok to ask a question here?
Juan Blanco
@juanfranblanco
sure
alan404
@alan404

but i will investigate for an intermidiate solution

Hi Juan is there a temporary solution for that? It will be much more convenient to have that function when browsing code. Thank you.

Juan Blanco
@juanfranblanco
I started it but the solidity team are working on the antlr
so I paused it as it was mainly a throw away effort
oppenheim
@oppenheim
Could you please also add support for the "immutable" keyword? Using it causes the parser to fail. Thanks!
Juan Blanco
@juanfranblanco
many thanks !!! @oppenheim please come over to discord for other thoughts
Juan Blanco
@juanfranblanco
@/all for any chat, support etc come to the discord channel above ^^^
dylankilkenny
@dylankilkenny
Hey, go to definition is not working for contracts built with sol 0.8
anyone know a fix?