Psilon

Add support for alloc::* types

8

Currently I have following errors: ``` error[E0277]: the trait bound `alloc::String: serde::Serialize` is not satisfied --> C:\Users\Alex\Documents\Repo\pwasm-abi\derive\src\json.rs:14:10 | 14 | #[derive(Serialize, Debug)] | ^^^^^^^^^ the trait `serde::Serialize` is not implemented...

Ignore clippy warnings in generated code

2

I think it worth adding ```rust #![allow(clippy::all, clippy::restriction, clippy::pedantic, clippy::nursery, clippy::cargo)] ``` to the existing `#![allow(dead_code, unused_imports)]` disabled warnings.

**Openapi.yaml** ```yaml x-generator: NSwag v13.3.0.0 (NJsonSchema v10.1.11.0 (Newtonsoft.Json v12.0.0.0)) openapi: 3.0.0 info: title: Settings API description: Settings and presets service version: v1 servers: - url: 'https://myUrl' paths: /: get: tags:...

Allow running individual tests with coverage

2

There is a workaround currently to run individual tests and get coverage for them: ```bash cargo llvm-cov --lcov --output-path lcov.info -- my::super::model::test_name --exact --nocapture ``` I think it is either...

Consider following code ```rust let postgres_manager = ConnectionManager::::new("postgre://bac"); let pool = Pool::new(postgres_manager)?; ``` Currently it produces following output: ``` 2020-05-13T16:30:07.777244900+03:00 ERROR r2d2 - missing "=" after "postgre://bac" in connection info...

Add an option to run without depending on openssl

1

I think rust-web3 is a great crate. However, there is an issue that crate currently has a hard depndency on `openssl` when using wss subscriptions. ```toml ws-tls-tokio = ["async-native-tls", "async-native-tls/runtime-tokio",...

Fix recursion

1

This PR fixes the problem with high `RetryCount` values. For example if you set it to 2000-4000 you will get an overflow. On my machine for ` RetryCount = 5000`...

It's basically an attempt to resolve all compiler warnings and make code more clean and readable.

Do not expect that first word in comment line is name of result variable

5

Consider following method and comment: ```solidity /// @return Some value function foo() external view returns(uint256) { return 0; } ``` When it get parsed with `parseNatSpec` function it parses `Some`...

Add returnParameters in SourceContractItem alongside with parameters

3

Current version of `solidity-docgen` exposes `ast.parameters` as `args` but doesn't expose return values. It's important because `natspec.returns` only shows return args that were documented which isn't always the case. It...