question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Feedback] Directory naming ambigouos

See original GitHub issue

Page: /start/getting-started/setup/q/integration/[integration]

Feedback:

Hi, thanks for the great tutorial!

The only thing that confused me a little was the difference between “your projects directory” and “From the root of the project”.

In the step “Initialize a new backend” it says “From the root of the project, run”. I wasn’t sure if this refers to the root of the react app that was referred to before (“Now that we’re in the root of the project”) or the parent folder that I considered the actual root of my project, referred to before as “From your projects directory”.

Since it sounded ambiguous and my (beginner’s) expectation was that the overall project would live outside of the frontend directory, I ran “amplify init” in the parent directory. But know I think that’s not intended, because amplify init placed aws-export.js in the …/src instead of ./src

I think I figured it out now, but future readers might benefit from a clarification in the tutorial.

Keep up the great work!

Issue Analytics

  • State:closed
  • Created a year ago
  • Reactions:1
  • Comments:6 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
Safadurimocommented, Oct 29, 2022

I ran into the exact same issue. @vimode , Go ahead and fix that!

1reaction
vimodecommented, Oct 8, 2022

Hello,

I would like to fix this small issue in the docs.

As per my understanding the amplify init command should be run while being in the react-amplified folder.

I think just clarifying that folder name wherever the term root of the project (2 instances) is used should give a clear understanding of the directory structure.

Thank you.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Active Directory: Ambiguous Name Resolution - TechNet Articles
Ambiguous Name Resolution can be used to retrieve information on any class of object in Active Directory.
Read more >
zsh: Ambiguous completion only to file/directory names
I'm trying to have zsh supplement underscores when completing a file/directory name. That is to say,
Read more >
Unable to modify/create a rule: Element name ambiguous ...
This error usually means the element appears on more than one dimension and TM1 can't sort out which one you are referencing.
Read more >
Establishing your researcher identity with ORCiD
An ORCiD is unique, eliminating name abiguity. One of the primary goals of the ORCID initiative is to solve the name ambiguity problem....
Read more >
Ambiguous Names with GIT? - branch - Stack Overflow
It usually is because you have the same name (than your branch) used in another namespace: like the "remotes" namespace: the name of...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found