mohamedelshami

@unqjohnny please take a look at this tutorial here: https://docs.web3j.io/4.8.7/getting_started/deploy_interact_smart_contracts/

Making this as resolved based on the latest comments

@Tilseroz @ffarhanaamin it appears that this no longer an issue

@kberezin-p6 I've pushed a temporary fix to ignore the failing integration test in master, are you please able to rebase so I can rerun checks before the merge?

Thanks, @kberezin-p6. There is a build error due to spottlessApply check. Could you run `./gradlew spotlessApply` please and commit again? Apologies, this workflow should probably improve to make this check...

I agree with the usefulness of having an accessible decode utility. I'm assuming the design decision behind keeping TypeDecoder and TypeEncoder package protected is intended, to keep them encapsulated inside...

@monperrus @monperrus my recommendation would still be to create a util class that extends FunctionalEncoder and DefaultFunctionalReturnDecoder to provide high-level shorthand APIs for these ABI decode/encode methods.

@monperrus happy to be pragmatic here and merge this for now, can you please add some documentation to what we've discussed about risk of breaking future compatibility and reference this...

Thanks, @monperrus. Can you please make that comment more explicit? e.g. "The public static methods can break future compatibility, and will likely replaced with high level util APIs"

@rampatra @herbig does working v4.8.4 or this is still an issue?