JavaScript: Naming styles
greeting is an example of a simple name, although not all of them are that simple. Often, they are a combination of several words. For example, "user password". Different languages have different naming styles for variables.
Four main variable naming conventions are sometimes combined. These conventions apply to variable names consisting of several words:
- kebab-case – a hyphen separates the parts of the name. For example,
my-super-var - snake_case - an underscore is used as a separator. For example,
my_super_var - CamelCase - each word in the name is capitalized. For example,
MySuperVar - lowerCamelCase - each word is capitalized except the first. For example,
mySuperVar
Javascript uses CamelCase and its variation lowerCamelCase, with the first letter of the first word in lowercase. We use lowerCamelCase for variables. It means we concatenate the words, and all the words apart from the first are capitalized: userName. With three words it looks like this: mySuperVariable.
Instructions
Create two variables named "first number" and "second number" using lowerCamelCase. Assign 11 to the first variable and -100 to the second. Print their product.
The code will work with any name, and we only check the printed result, so the task is up to you.
If you've reached a deadlock it's time to ask your question in the «Discussions». How ask a question correctly:
- Be sure to attach the test output, without it it's almost impossible to figure out what went wrong, even if you show your code. It's complicated for developers to execute code in their heads, but having a mistake before their eyes most probably will be helpful.
Tests are designed so that they test the solution in different ways and against different data. Often the solution works with one kind of input data but doesn't work with others. Check the «Tests» tab to figure this out, you can find hints at the error output.
It's fine. 🙆 One task in programming can be solved in many different ways. If your code passed all tests, it complies with the task conditions.
In some rare cases, the solution may be adjusted to the tests, but this can be seen immediately.
It's hard to make educational materials that will suit everyone. We do our best but there is always something to improve. If you see a material that is not clear to you, describe the problem in “Discussions”. It will be great if you'll write unclear points in the question form. Usually, we need a few days for corrections.
By the way, you can participate in courses improvement. There is a link below to the lessons course code which you can edit right in your browser.
Your exercise will be checked with these tests:
// @ts-check
import { expect, test, vi } from 'vitest'
test('hello world', async () => {
const consoleLogSpy = vi.spyOn(console, 'log').mockImplementation(() => { });
await import('./index.js')
const firstArg = consoleLogSpy.mock.calls.join('\n');
expect(firstArg).toBe('-1100')
})Teacher's solution will be available in:
20:00
