package.jsonis. If we found any packages, their paths will be displayed in the drop-down menu when you click on this field. You can leave it empty to set it as your root directory (
/), or input your own path, even if we didn't detect it. Why do we need this information? Let's say, for example, you have a single repository for both the backend and the frontend of your project, but the texts you'd interact with are (most likely) in the frontend. So, in order for us to narrow down where to look for them, you'd want your base directory to be
frontendis the name of your frontend directory).
Text resources formatif the format you chose isn't hardcoded (JSON or PO). If found, this field will display the generalized paths of the text resources as options in the drop-down menu of this field, with numbers next to each option which represent the number of resources found in each path, but you can enter a new path if you wish. Important note - this path is relative to the Base directory's path which you've input earlier. So, if your Base directory is
frontend/, and your text resources are under
frontend/src/langs/*.json, what you'd want to enter in this field is
.flycode.yamlfile for your repository, that'll let us know where to look for your text resources. As suggested at the bottom of the page, you can also add a
.flycode.yamlmanually, or tweak it later as needed. A documentation regarding this file and its options can be found in this section of our docs.