This is a practical mini-tutorial you can follow (and reuse) to get Move language support in Neovim with lazy.nvim using Lua config.
It is assumed that neovim (0.11) is installed and is using lua for its configurations. Its also assumed that the configuration is under: ~/.config/nvim
Create:
~/.config/nvim/ftdetect/move.lua
I am Nikolaos Kontakis, starting in the beginning of 2021 as a Parity employee until today, I work on Polkadot related projects, mainly on Substrate-Connect and Zombienet. In addition to my professional commitments, I have dedicated my free time to crafting small applications (e.g. polkadot-notify.me MVP which is currently being refactored and rebuild) and contributing to open-source initiatives. I am a member of @polkadot{.js}, Polkadot Blockchain Academy. Especially in PolkadotJS, I've made contributions to Polkadot-js apps and API, particularly in the context of the integration with substrate-connect and light clients; I am a Polkadot Blockchain Academy Alumni from Cohort #2 (Buenos Aires), where I contributed to but also supported (with several integrations and code-improvements) the [presentation project of the
| // TODO | |
| import { deferred } from "../../deps/std/async.ts"; | |
| import { assertExists, assertNotInstanceOf } from "../../deps/std/testing/asserts.ts"; | |
| import { ProviderListener } from "./base.ts"; | |
| import { smoldotProvider } from "./smoldot.ts"; | |
| const WESTEND_CHAIN_SPEC_URL = | |
| "https://raw.githubusercontent.com/paritytech/substrate-connect/main/packages/connect/src/connector/specs/westend2.json"; | |
| // For some reasin westmint does not initializes. We need to find a more updated chainspec (or some other spec) |
The last few weeks I've been prototyping an alternative to polkadot-js/api. My goal is to create a more modular, user-friendly, strongly-typed and light-weight version of polkadot-js/api.
I'm still not sure whether I will be able to accomplish those goals. However, I certainly hope that I will be able to share the knowledge and ideas that I gather during this attempt. That's why I'm creating this gist.
I'm not a technical writer, and I don't have a lot of time to spend on writing this. So, this is meant to be a "brain dump". Although, hopefully someone who is good at writing documentation can use this for improving the substrate docs site.
This repo is meant as a step-by-step guide on how to setup a React project (non CRA) with Webpack (v5 with Babel), and @substrate/connect (light client in-browser) in order to kick-off your first dApp. (Note: This repo is on purpose built without CRA and it is meant as a guideline for devs who wants to start their dApp without CRA but with Webpack. There are two different repos following the installation with Parcel (v2) and pending CRA.)
To learn more and understand what is a light-client - here is a helpful article.
Before starting with the installation steps which will include explanation of what is what, first of all a small intro on each main component of this dApp:
