open-index/open-npm huggingface dataset:
npm package: @firestitch/checkbox
Description: ## Installation
Author: Maksim Sergeev
Latest version: 0.1.0

# fs-address

## Installation

To install this library, run:

```bash
$ npm install fs-address --save
```

## Consuming your library

Once you have published your library to npm, you can import your library in any Angular application by running:

```bash
$ npm install fs-address
```

and then from your Angular `AppModule`:

```typescript
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';

import { AppComponent } from './app.component';

// Import your library
import { SampleModule } from 'fs-address';

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,

    // Specify your library as an import
    LibraryModule
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }
```

Once your library is imported, you can use its components, directives and pipes in your Angular application:

```xml
<!-- You can now use your library component in app.component.html -->
<h1>
  {{title}}
</h1>
<sampleComponent></sampleComponent>
```

## Development

To generate all `*.js`, `*.d.ts` and `*.metadata.json` files:

```bash
$ npm run build
```

To lint all `*.ts` files:

```bash
$ npm run lint
```

## License

MIT © [Maksim Sergeev](mailto:sergeev.maxs@gmail.com)
npm package: @firestitch/codegenerator
Description: ## Installation
Latest version: 18.0.13

# Running Code Generator and Schematics From Source

## Installation

1. Clone repo `git clone git@github.com:Firestitch/ngx-code-generator.git`
2. `npm install`
3. At this step we have to build our package for future using inside this project
`npm run package`
4. When package build finishes we need to start using `dist` folder as schematic source
   - `cd dist`
   - `npm link`
   - `cd ..`
   - `npm link @firestitch/codegenerator`
   
5. All done!

## Development

In `/apps` folder we have 3 different projects:
- api
- code-generator
- playground


### Api Project

This project constains backend part of code generator. It receives API calls from CodeGenerator in browser
and run schematics with passed parameters.

Its just simple NodeJS server

### Code-generator

This is frontend part of code generator. Contains Angular application

### Playground

Playground is a sandbox project where actual code generator can be tested.

## Where is Schematics code?

Schematics code placed in `/libs/schematics`


## How to run Dev Server?

Dev server is not single application and you have to start 3 different servers

1. `npx nx serve code-generator`
2. `npx nx serve api '--args=--root=project' --verbose=true` 
3. `npm run watch:schematics`

Manual generation of schematics if you are not watching run on every change
1. `npm run package`


## Build & Publish

Use `npm run package` for build and `npm run package:publish` for publishing your changes



## Debug Schematics

1. node --inspect-brk ./node_modules/.bin/schematics .:dialog  --name=testa   --module=common.module.ts   --path=project/common   --included-module-exports=false   --routable-component=undefined   --route-observer=undefined   --titled-component=false --dry-run=false
2. open in browser chrome://inspect
npm package: @firestitch/lint
Description: @firestitch/ngx-lint
Latest version: 18.0.20

# Angular HTML Formatting Guide

## Basic Elements

### Empty Elements
Elements with no content and either no attributes or a single attribute should be on one line:
```html
<custom-element></custom-element>
<button class="primary"></button>
```

### Single-Line Elements
Elements with content but no attributes, or with a single attribute, should be on one line:
```html
<span>Short text</span>
<br>
```

### Elements with Single Attribute
Always keep element and its single attribute on the same line:
```html
<div class="container"></div>
<button (click)="onClick()"></button>
<input type="text">
```

## Multi-Attribute Elements

### With Content
When an element has multiple attributes AND content:
- Opening tag on its own line
- Attributes indented with 4 spaces/2 indents
- Each attribute on its own line
- Content indented with 2 spaces/1 indent
- Closing tag aligned with opening tag
```html
<div
    class="container"
    [attr]="value"
    (click)="onClick()">
  Some content here
</div>
```

### Without Content
When an element has multiple attributes but NO content:
- Opening tag on its own line
- Attributes indented with 2 spaces/1 indent
- Each attribute on its own line
- Closing tag on new line, aligned with opening tag
```html
<app-header
  class="main-header"
  [title]="pageTitle"
  (menuClick)="onMenuClick()">
</app-header>
```

## Comments
Comments should be preserved exactly as written in source:
```html
<!-- This comment stays exactly as is -->

<!--
  Multi-line comments
  preserve their
  formatting
-->
```

## Angular Control Flow Syntax
Control flow blocks should be properly indented:
```html
@if (condition) {
  <div>Content</div>
} @else if (otherCondition) {
  <div>Other content</div>
} @else {
  <div>Default content</div>
}

@for (item of items) {
  <div>{{ item }}</div>
}
```

## Interpolation
Interpolation should have consistent spacing:
```html
<div>{{ value }}</div>
<span>Prefix {{ value }} suffix</span>
```

## Nested Elements
Each nesting level adds 2 spaces of indentation(double indents):
```html
<div class="parent">
  <div
      class="child"
      [attr]="value">
    <span>Content</span>
  </div>
</div>
```

## Self-Closing Tags
Self-closing tags should remain self-closing and on one line:
```html
<input type="text">
<input
  type="text"
  name="email">
<br>
```
npm package: @firestone-hs/bgs-global-stats
Description: Used this project as template: https://github.com/alukach/aws-sam-typescript-boilerplate
Latest version: 1.0.57

# Reference

Used this project as template: https://github.com/alukach/aws-sam-typescript-boilerplate

# Random notes for Quests

what do we want to get?

-   average turns to complete for given hero / tribes (and current MMR bracket)
-   how much the current hero influences the turns to complete (i.e. delta vs average of heroes)
-   how much the current tribes influence the turns to complete (i.e. delta vs all tribes). Maybe also highlight the tribes that have the best influence, as these are probably tribes you should focus on? Maybe this is too obvious?

stat: {
globalData;
difficulty: <difficult, globalDataForDifficulty, difficultyImpact>
heroes: <hero, globalDataForHero>
tribes: <tribe, globalDataForTribe, raceAverageTurnToCompleteImpact, raceCompletionRateImpact>
}

in game: - for each quest - extract quest + difficulty - get turnsToComplete + completionRate for hero - get raceImpact for turnsToComplete + completionRate for each tribe - get difficultyImpact for tTC + cR for the difficulty. - this will tell me that "on average, difficulty 4 is + 0.5 ttc vs average difficulty) - build average turn to complete for hero + tribes (using the race impacts) + difficulty (using the average delta for difficulty. That way we can use the global average for the hero, and use the difficulty delta to update this data. The assumption behind this is that the difficulty impact all heroes the same way, which a priori seems fair, since the difficulty is just a quota to get)

globalData: averageTurnToComplete (when completed), completionRate

```

```
npm package: @firestone-hs/build-global-stats
Description: ``` rm -rf dist && tsc && rm -rf dist/node_modules && 'cp' -rf dist/ /g/Source/zerotoheroes/firestone/core/node_modules/\@firestone-hs/build-global-stats/ rm -rf dist && tsc && rm -rf dist/node_modules && npm publish --access public ```
Latest version: 1.0.8

# Deploy

```
rm -rf dist && tsc && rm -rf dist/node_modules && 'cp' -rf dist/ /g/Source/zerotoheroes/firestone/core/node_modules/\@firestone-hs/build-global-stats/
rm -rf dist && tsc && rm -rf dist/node_modules && npm publish --access public
```

# Reference

Used this project as template: https://github.com/alukach/aws-sam-typescript-boilerplate
npm package: @firestone-hs/categorize-deck
Description: ``` npm run build && sam local invoke -t template.yaml -e event.json CategorizeDeckFunction ```
Latest version: 1.0.4

# Test it

```
npm run build && sam local invoke -t template.yaml -e event.json CategorizeDeckFunction
```

# Deploy

```
npm run build && npm run package && npm run deploy

rm -rf dist && tsc && rm -rf dist/node_modules && npm publish --access=public
```

# Reference

Used this project as template: https://github.com/alukach/aws-sam-typescript-boilerplate