Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial![](https://ecs-static.teamtreehouse.com/assets/views/marketing/shared/community-banner-white-47072046c51352fe6a69f5e691ff5700b28bb11d45197d7bdf066d9ea3f72d0c.webp)
![Anish Palan](https://secure.gravatar.com/avatar/b4a4b0a6766a2ca9a6c96227a270a71c?s=96&d=https%3A%2F%2Fecs-static.teamtreehouse.com%2Fassets%2Fcontent%2Fdefault_avatar-445fbbabfc8dc9188fb5967fe43322ee0c3e0dd1e10f378bf8343784af5a13eb.webp&r=pg)
Anish Palan
3,157 PointsSignificance of the parameter in {} in @RequestMapping (value= "/gifs/{gifId}/edit")
While running my application the {gifId} was misspelled as {dgifI} so I wasnt getting the correct edit page which is supposed to be shown on clicking edit link. How do we decide what to put in {} ?
1 Answer
![Alexander Nikiforov](https://uploads.teamtreehouse.com/production/profile-photos/5494222/micro_IMG_0409.jpg)
Alexander Nikiforov
Java Web Development Techdegree Graduate 22,175 PointsIt does not matter what to put in @RequestMapping(value = "/gifs/{gifid}") as long as later in @PathVariable you re-type correctly what was in @RequestMapping, e.g. this is right :
@RequestMapping(value = "/gifs/{someId}")
public String someMethod(@PathVariable("someId") int actualSomeIdToBeUsed)
As long as someId
in the example in @PathVariable and @RequestMapping are same, it does not matter how you call it.
Boban Talevski
24,793 PointsBoban Talevski
24,793 PointsAnd I suppose Chris had intentionally left it misspelled there (I know I would now that I saw it :P), which was an interesting thing to catch while implementing the gif update and upload methods. Guess the point was, don't assume any of the present code is perfectly working and look for weird typos which won't be caught at compile time. Now I know better for sure :).