Skip to content

Move pl/handbook-v1/The Handbook.md #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

jihoon-seo
Copy link
Contributor

@github-actions
Copy link
Contributor

Thanks for the PR!

This section of the codebase is owned by @msieroslawska and @TomWebwalker - if they write a comment saying "LGTM" then it will be merged.

@github-actions
Copy link
Contributor

Translation of The Handbook.md

title: TypeScript Guide
layout: docs
permalink: /pl/docs/handbook/intro.html

oneline: Your first steps in learning TypeScript

A few words about the Guide

Almost 20 years after its insistance, JavaScript is today one of the most widely used programming languages created to date. Initially, it was an inconspicuous scripting language used on websites to add simple interactive elements, but over time it greatly increased its size and capabilities, being now often chosen in the frontend and backend of applications of every possible size. Although both the size, application, and complexity of JavaScript programs is rapidly increasing, the ability of javascript to determine the relationships between different elements of code has remained constant. Rather peculiar semantics combined with this very difference between the complexity of the language and the programs written in it have created an uncomfortable situation, where the development of new software has become extremely difficult on a larger scale.

The most common errors made by programmers and programmers can be described as type errors: a specific value was used where a different type of value was expected. The main reasons for such errors are usually simple typos, ignorance of the programming interface (API) of the external library used, or incorrect predicted result of the program being run. TypeScript wants to be a static type controller for programs written in JavaScript - in other words, a tool that works in a static way against the right code by validate the types in the program.

If you are taking your first steps in TypeScript without knowledge of JavaScript or another programming language, we encourage you to read JavaScript guide in mozilla documentation.
If you already have experience in other programming languages, javascript syntax should quickly become understandable to you after reading the Guide.

Organization of the Guide

The TypeScript guide is divided into two sections:

  • Guide

    The TypeScript Guide aims to be a comprehensive source of knowledge needed to create everyday code. The recommended reading order is the articles available in the navigation on the left, from top to bottom.

    Each chapter and page should provide you with extensive knowledge of each issue. The TypeScript guide, however, is not a comprehensive specification of the language, but rather an in-depth guide to all its functionalities and features.

    Reading the Guide should teach you:

    • How to read and understand the most commonly used TypeScript syntax
    • How to explain the effects of the compiler's most important options
    • how to correctly anticipate system behaviour in the most common cases,
    • how to create a .d.ts declaration for a simple function, object, or class.

    To maintain maximum clarity and brevity, the main part of the Guide does not focus on edge cases. Details of such situations can be found in the source materials.

  • References

    The source materials section is designed to cover each TypeScript functionality with a comprehensive explanation of how it operates. Although, of course, these articles can be read as the main part of the Guide - from top to bottom - however, due to the much deeper development of each concept, the source materials are not dependent on each other.

Other objectives

The guide was written in the most concise way so that its reading does not last more than a few hours. For this reason, some topics are not discussed in depth.

First of all, the guide is not intended to explain basic JavaScript notes such as features, classes, or location. Wherever possible, links to external materials are provided, recommended as additional reading for the purpose of familiarising yourself with these topics.

This guide is also not a substitute for language specifications. In special cases, articles omit descriptions of boundary cases or definitions of individual system behaviors to ensure that the topic is as simple and transparent as possible. In-depth definitions are available as separate resources in source materials. However, these materials are not intended as a source of knowledge for beginners, as the advanced vocabulary and related topics used in them may not be known to you yet.

Unless necessary, the Guide also does not explain how TypeScript works with other tools. TypeScript connection configurations with webpack, rollup, parcel, react, babel, closure, lerna, rush, bazel, preact, vue, angular, svelte, jquery, yarn or npm are outside the scope of the Guide - in such cases, we recommend that you search for the right resources on the internet.

How do I get started?

Before you start reading about Base Types we recommend that you review one of the following pre-pages that highlight key similarities and differences between TypeScript and your favorite language and explain the most common misconceptions specific to those languages.

Generated by 🚫 dangerJS against 7e58243

@orta
Copy link
Contributor

orta commented Mar 12, 2021

Oh yeah, this was my fault (in switching things for the v2 launch) - thanks for the PR!

@orta orta merged commit 1fa19ca into microsoft:main Mar 12, 2021
@jihoon-seo jihoon-seo deleted the 210312-Move-pl/handbook-v1/The_Handbook.md branch March 12, 2021 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

A file causes 'local-validate' CI to fail
2 participants