Hey, folks in this video let's take a quick look at how the manifest file works.
On the subquery home page here let's click on documentation
and we'll jump in to create a project manifest file here you can see that
the file is also known as project. YAML can be seen as the entry point of your project
defining most of the details on how SubQuery will index and transform the chain data,
in other words, this is like your configuration or your config file providing information such
as your repository the location of your schema information about your network
and also data sources you can go ahead and read this particular page here in the documentation
but let's jump into the code and I'll show you how it works let's go ahead and create the standard
startup project we'll go subql init and I can go ahead and provide the name of the project here or
if I leave this blank and hit enter I can also provide it here as well if I leave it blank it
will take subql starter as default so let's go demo project hit enter my good repository here
with the endpoint, the default is Polkadot production mainnet
the author is mandatory so let's go something like supposed to Harry Potter but potty will do
with my version let's make it triple one
and you can see the scaffolding of the project appear on the left-hand side let's go ahead and
open up the manifest file here and I'll also open up the package.json file just to the side
now with the project name demo project, you can see that this appears in the package.json file
up here the git repository this appears in the repository key in my manifest file
the endpoint it also appears in the manifest file here the author you'll see it appears in the
package.json file along with the version triple one-up above and the license as well taking a
closer look at the manifest file you'll see the spec version indicates the version of the manifest
file structure that you're working with as the subquery dev team makes improvements this number
will increment the schema key here points to the location of your schema.graphql file so this
file here on the left hand side and the network as we saw before pointing to the
polka dot mainnet the dictionary is a neat feature if you don't want to include this
you can always exclude it by commenting it out but it is highly recommended to use this
and if you're not sure what the dictionary does you can always jump into the documentation here
under tutorials and examples and click on how does a sub query dictionary work
within data sources you've got the name and then you've got the kind which is equal to
substrate runtime now this is the only value that you can put in here for now as highlighted
by here in the documentation and of course the start block where you can modify this to start
at any particular block height that you want and again to get more information on the block height
you can go into the tutorials here and you can see we've got how to start at a different block height
going through and explaining why you'd want to not start from zero for example
below this comes the interesting part where we've got the mappings grouped into three
different handler types we've got the block the event and the call as well and then filters
within in subsequent videos we'll take a closer look at network endpoints and network filters
along with mapping filters as well but that's it for now just a very high-level overview of how
the manifest file works remembering that it's a configuration file that when you modify or update
you won't have to rebuild your application thanks for watching as always catch you next time you