We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Related to issue: FuelLabs/fuels-ts#1960
TypeScript code snippets have import statements, which aren't being rendered correctly (examples below).
// #import { bn, Contract, FunctionInvocationResult };
import { FunctionInvocationResult, Contract, bn } from 'fuels';
The fuels-ts docs has a custom plugin which renders our code snippet imports.
fuels-ts
I believe there is work to be done on both repositories, so it would be good to align on this.
Code snippet imports to be rendered correctly.
e.g. import { FunctionInvocationResult, Contract, bn } from 'fuels';
Code snippet imports are not rendered.
e.g. // #import { bn, Contract, FunctionInvocationResult };
The text was updated successfully, but these errors were encountered:
I believe I can make this fix on the docs-hub side without any changes in the fuels-ts repo, thanks!
Sorry, something went wrong.
This should be resolved on the Fuels TS side:
Closing issue.
No branches or pull requests
Related to issue: FuelLabs/fuels-ts#1960
Summary
TypeScript code snippets have import statements, which aren't being rendered correctly (examples below).
// #import { bn, Contract, FunctionInvocationResult };
import { FunctionInvocationResult, Contract, bn } from 'fuels';
The
fuels-ts
docs has a custom plugin which renders our code snippet imports.I believe there is work to be done on both repositories, so it would be good to align on this.
Expected
Code snippet imports to be rendered correctly.
e.g.
import { FunctionInvocationResult, Contract, bn } from 'fuels';
Actual
Code snippet imports are not rendered.
e.g.
// #import { bn, Contract, FunctionInvocationResult };
The text was updated successfully, but these errors were encountered: