Step 3 - Repository Scan
For us to know where to help, we need to know where it hurts!
After selecting the repository you want to connect with FlyCode, we will scan your code for text resources. Whether they are hardcoded in React, or stored in an i18n JSON, we should find them!
Initially, you should see the scanning taking place:
Scanning your repository for text resources

Scan Succeeded

Once the scan is finished, if all went smoothly, this is what you should see:
Scan was successful and resources were found!
Here, we give you some information about what we managed to find. In the example above, you can see we:
  • Found a few files in your project that contain text.
  • Saw that you manage 2 web projects - AKA we saw 2 package.json files in different directories.
  • Didn't find a web framework that you're using.
  • Didn't find any i18n libraries - no text JSONs.
  • Found a few hardcoded texts in your code.
Below, we can see an example of one of the texts we found, and in which context it was found: we saw it was in a component, as indicated above the text. We also determined that this text is in English.
If you're satisfied with what we've found, you can proceed to the next (and final!) step by clicking the Complete configuration button. If, for some reason you think the scan didn't pick up on some stuff, feel free to contact us (link can be found at the bottom of this page)!

Scan Failed

If for some reason the scan failed, you should see this:
Scan failed :(
In this case, you can try the following:
  • Click the Try again button - this might be on us and we'll be glad to give it another go!
  • Pick another repository - maybe you'd like to connect something else?
  • Contact us - please schedule a session with us at a time convenient to you using our Calendly calendar (link can be found at the bottom of this page).
Or, alternatively, you might see this:
Scan succeeded but no resources found
This means that our scan was successfully done, but we didn't find any text resources within your repository. This might be because you don't have any text resources in your repository, in which case you can pick a different repository.
If you think this is a mistake, you can contact us (link can be found at the bottom of this page) and we'll solve it together.

Book a session with us here, or contact us here.

Copy link