mirror of
https://github.com/Raghu-Ch/angular-challenges.git
synced 2026-02-11 05:13:02 -05:00
chore(): revert challenge object change
This commit is contained in:
Eduardo Roth
@@ -16,11 +16,7 @@ const docs = defineCollection({
|
||||
docsSchema({
|
||||
extend: z.object({
|
||||
noCommentSection: z.boolean().optional().default(false),
|
||||
challenge: z
|
||||
.object({
|
||||
number: z.union([z.number(), z.boolean()]).default(false),
|
||||
})
|
||||
.optional(),
|
||||
challengeNumber: z.union([z.number(), z.boolean()]).default(false),
|
||||
author: reference('authors').optional(),
|
||||
command: z.string().optional(),
|
||||
blogLink: z.string().optional(),
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟢 Projection
|
||||
description: Challenge 1 is about learning how to project DOM element through components
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 1
|
||||
challengeNumber: 1
|
||||
command: angular-projection
|
||||
blogLink: https://medium.com/@thomas.laforge/create-a-highly-customizable-component-cc3a9805e4c5
|
||||
videoLink:
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🔴 Utility Wrapper Pipe
|
||||
description: Challenge 10 is about creating a pipe to wrap utilities
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 10
|
||||
challengeNumber: 10
|
||||
command: angular-pipe-hard
|
||||
sidebar:
|
||||
order: 202
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Highly Customizable CSS
|
||||
description: Challenge 13 is about creating highly customizable CSS styles
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 13
|
||||
challengeNumber: 13
|
||||
command: angular-styling
|
||||
sidebar:
|
||||
order: 104
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🔴 Master Dependancy Injection
|
||||
description: Challenge 16 is about masjering how dependancy injection works
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 16
|
||||
challengeNumber: 16
|
||||
command: angular-di
|
||||
sidebar:
|
||||
order: 203
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟢 Anchor Navigation
|
||||
description: Challenge 21 is about navigating inside the page with anchor
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 21
|
||||
challengeNumber: 21
|
||||
command: angular-anchor-scrolling
|
||||
sidebar:
|
||||
order: 4
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟢 @RouterInput()
|
||||
description: Challenge 22 is about using the @Input decorator to retreive router params.
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 22
|
||||
challengeNumber: 22
|
||||
command: angular-router-input
|
||||
blogLink: https://medium.com/ngconf/accessing-route-params-in-angular-1f8e12770617
|
||||
sidebar:
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Directive Enhancement
|
||||
description: Challenge 3 is about enhancing a built-in directive
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 3
|
||||
challengeNumber: 3
|
||||
command: angular-ngfor-enhancement
|
||||
blogLink: https://medium.com/@thomas.laforge/ngfor-enhancement-716b44656a6c
|
||||
sidebar:
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🔴 Interoperability Rxjs/Signal
|
||||
description: Challenge 30 is about learning how to mix signal with Rxjs
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 30
|
||||
challengeNumber: 30
|
||||
command: angular-interop-rxjs-signal
|
||||
sidebar:
|
||||
order: 204
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟢 Module to Standalone
|
||||
description: Challenge 31 is about migrating a module based application to a standalone application.
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 31
|
||||
challengeNumber: 31
|
||||
command: angular-module-to-standalone
|
||||
sidebar:
|
||||
order: 6
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Change Detection Bug
|
||||
description: Challenge 32 is about debugging an application that has issue when change detection is triggered
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 32
|
||||
challengeNumber: 32
|
||||
command: angular-bug-cd
|
||||
blogLink: https://medium.com/ngconf/function-calls-inside-template-are-dangerous-15f9822a6629
|
||||
sidebar:
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Decoupling Components
|
||||
description: Challenge 33 is about decoupling two strongly coupled components using Injection Token
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 33
|
||||
challengeNumber: 33
|
||||
command: angular-decoupling
|
||||
sidebar:
|
||||
order: 106
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 InjectionToken
|
||||
description: Challenge 39 is about learning the power of dependancy injection
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 39
|
||||
challengeNumber: 39
|
||||
command: angular-injection-token
|
||||
sidebar:
|
||||
order: 118
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🔴 Typed ContextOutlet
|
||||
description: Challenge 4 is about strongly typing ngContextOutlet directives
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 4
|
||||
challengeNumber: 4
|
||||
command: angular-context-outlet-type
|
||||
blogLink: https://medium.com/@thomas.laforge/ngtemplateoutlet-type-checking-5d2dcb07a2c6
|
||||
sidebar:
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟢 Crud application
|
||||
description: Challenge 5 is about refactoring a crud application
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 5
|
||||
challengeNumber: 5
|
||||
command: angular-crud
|
||||
sidebar:
|
||||
order: 2
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Structural Directive
|
||||
description: Challenge 6 is about creating a structural directive to handle permissions
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 6
|
||||
challengeNumber: 6
|
||||
command: angular-permissions
|
||||
blogLink: https://medium.com/@thomas.laforge/create-a-custom-structural-directive-to-manage-permissions-like-a-pro-11a1acad30ad
|
||||
sidebar:
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟢 Pure Pipe
|
||||
description: Challenge 8 is about creating a pure pipe
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 8
|
||||
challengeNumber: 8
|
||||
command: angular-pipe-easy
|
||||
blogLink: https://medium.com/ngconf/deep-dive-into-angular-pipes-c040588cd15d
|
||||
sidebar:
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Wrap Function Pipe
|
||||
description: Challenge 9 is about creating a pipe to wrap component fonctions
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 9
|
||||
challengeNumber: 9
|
||||
command: angular-pipe-intermediate
|
||||
blogLink: https://medium.com/ngconf/boost-your-apps-performance-by-wrapping-your-functions-inside-a-pipe-7e889a901d1d
|
||||
sidebar:
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Control Value Accessor
|
||||
description: Challenge 41 is about creating a custom form control that implements Control Value Accessor interface.
|
||||
author: stanislav-gavrilov
|
||||
challenge:
|
||||
number: 41
|
||||
challengeNumber: 41
|
||||
command: forms-control-value-accessor
|
||||
sidebar:
|
||||
order: 1
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Effect vs Selector
|
||||
description: Challenge 2 is about learning the difference between effects and selectors in NgRx
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 2
|
||||
challengeNumber: 2
|
||||
command: ngrx-effect-selector
|
||||
blogLink: https://medium.com/@thomas.laforge/ngrx-effect-vs-reducer-vs-selector-58337ab59043
|
||||
sidebar:
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🔴 Power of Effect
|
||||
description: Challenge 7 is about creating an Ngrx effect with another Rxjs Hot observable
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 7
|
||||
challengeNumber: 7
|
||||
command: ngrx-notification
|
||||
sidebar:
|
||||
order: 206
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🔴 Extend Lib Generator
|
||||
description: Challenge 25 is about creating a Nx generator to extend the built-in Library Generator
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 25
|
||||
challengeNumber: 25
|
||||
sidebar:
|
||||
order: 207
|
||||
---
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Component Generator
|
||||
description: Challenge 26 is about creating a Nx generator to create a custom component
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 26
|
||||
challengeNumber: 26
|
||||
sidebar:
|
||||
order: 116
|
||||
---
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟢 Custom Eslint Rule
|
||||
description: Challenge 27 is about creating a custom Eslint Rule to forbid enums
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 27
|
||||
challengeNumber: 27
|
||||
sidebar:
|
||||
order: 12
|
||||
---
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Optimize Change Detection
|
||||
description: Challenge 12 about optimizing the number of change detection cycle while scrolling
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 12
|
||||
challengeNumber: 12
|
||||
command: performance-scroll-cd
|
||||
sidebar:
|
||||
order: 107
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟢 Default vs OnPush
|
||||
description: Challenge 34 is about learning the difference between Default and OnPush Change Detection Strategy.
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 34
|
||||
challengeNumber: 34
|
||||
command: performance-default-onpush
|
||||
sidebar:
|
||||
order: 7
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟢 Memoization
|
||||
description: Challenge 35 is about learning how pure pipe works
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 35
|
||||
challengeNumber: 35
|
||||
command: performance-memoized
|
||||
sidebar:
|
||||
order: 8
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟢 NgFor Optimization
|
||||
description: Challenge 36 is about learning how trackby works
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 36
|
||||
challengeNumber: 36
|
||||
command: performance-ngfor-optimize
|
||||
sidebar:
|
||||
order: 13
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Optimize Big List
|
||||
description: Challenge 37 is about learning how virtualization optimize big list rendering
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 37
|
||||
challengeNumber: 37
|
||||
command: performance-ngfor-biglist
|
||||
sidebar:
|
||||
order: 117
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Web workers
|
||||
description: Challenge 40 is about learning how to create and use a web worker
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 40
|
||||
challengeNumber: 40
|
||||
command: performance-christmas-web-worker
|
||||
sidebar:
|
||||
order: 119
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 High Order Operator Bug
|
||||
description: Challenge 11 is about resolving a Rxjs bug because of high order operators
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 11
|
||||
challengeNumber: 11
|
||||
command: rxjs-pipe-bug
|
||||
sidebar:
|
||||
order: 114
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟢 Race Condition
|
||||
description: Challenge 14 is about race condition in Rxjs
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 14
|
||||
challengeNumber: 14
|
||||
command: rxjs-race-condition
|
||||
sidebar:
|
||||
order: 11
|
||||
|
||||
@@ -3,8 +3,7 @@ title: 🟢 catchError
|
||||
description: Challenge 38 is about learning obervable completion.
|
||||
author: devesh-chaudhari
|
||||
command: rxjs-catch-error
|
||||
challenge:
|
||||
number: 38
|
||||
challengeNumber: 38
|
||||
sidebar:
|
||||
order: 14
|
||||
---
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Router
|
||||
description: Challenge 17 is about testing the router
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 17
|
||||
challengeNumber: 17
|
||||
command: testing-router-outlet
|
||||
sidebar:
|
||||
order: 108
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Nested Components
|
||||
description: Challenge 18 is about testing nested components
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 18
|
||||
challengeNumber: 18
|
||||
command: testing-nested
|
||||
sidebar:
|
||||
order: 109
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Input Output
|
||||
description: Challenge 19 is about testing inputs and ouputs
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 19
|
||||
challengeNumber: 19
|
||||
command: testing-input-output
|
||||
sidebar:
|
||||
order: 110
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Modal
|
||||
description: Challenge 20 is about testing modals
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 20
|
||||
challengeNumber: 20
|
||||
command: testing-modal
|
||||
sidebar:
|
||||
order: 111
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟢 Harness
|
||||
description: Challenge 23 is about testing with component harnesses
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 23
|
||||
challengeNumber: 23
|
||||
command: testing-harness
|
||||
sidebar:
|
||||
order: 9
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Harness Creation
|
||||
description: Challenge 24 is about creating a component harness.
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 24
|
||||
challengeNumber: 24
|
||||
command: testing-create-harness
|
||||
sidebar:
|
||||
order: 112
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟢 Checkbox
|
||||
description: Challenge 28 is about testing a simple checkbox
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 28
|
||||
challengeNumber: 28
|
||||
command: testing-checkbox
|
||||
sidebar:
|
||||
order: 10
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🔴 Real-life Application
|
||||
description: Challenge 29 is about testing a real-life application
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 29
|
||||
challengeNumber: 29
|
||||
command: testing-todos-list
|
||||
sidebar:
|
||||
order: 205
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟠 Function Overload
|
||||
description: Challenge 15 is about creating overload functions
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 15
|
||||
challengeNumber: 15
|
||||
command: typescript-overload
|
||||
blogLink: https://medium.com/ngconf/function-overloading-in-typescript-8236706b2c05
|
||||
sidebar:
|
||||
|
||||
@@ -2,9 +2,7 @@
|
||||
title: 🟢 Proyección
|
||||
description: Desafio 1 trata sobre aprender a proyectar elementos del DOM a través de componentes,
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
label: Reto
|
||||
number: 1
|
||||
challengeNumber: 1
|
||||
command: angular-projection
|
||||
blogLink: https://medium.com/@thomas.laforge/create-a-highly-customizable-component-cc3a9805e4c5
|
||||
videoLink:
|
||||
|
||||
@@ -2,9 +2,7 @@
|
||||
title: 🟢 @RouterInput()
|
||||
description: El desafío 22 trata sobre el uso del decorador @Input para utilizar parámetros del router.
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
label: Reto
|
||||
number: 22
|
||||
challengeNumber: 22
|
||||
command: angular-router-input
|
||||
blogLink: https://medium.com/ngconf/accessing-route-params-in-angular-1f8e12770617
|
||||
sidebar:
|
||||
|
||||
@@ -2,9 +2,7 @@
|
||||
title: 🟠 Mejorar Directiva
|
||||
description: El desafío 3 se trata de una directive incorporada.
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
label: Reto
|
||||
number: 3
|
||||
challengeNumber: 3
|
||||
command: angular-ngfor-enhancement
|
||||
blogLink: https://medium.com/@thomas.laforge/ngfor-enhancement-716b44656a6c
|
||||
sidebar:
|
||||
|
||||
@@ -2,9 +2,7 @@
|
||||
title: 🟠 InjectionToken
|
||||
description: Desafio de Angular 39 para aprender sobre el poder del InjectionToken
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
label: Reto
|
||||
number: 39
|
||||
challengeNumber: 39
|
||||
command: angular-injection-token
|
||||
sidebar:
|
||||
order: 118
|
||||
|
||||
@@ -2,9 +2,7 @@
|
||||
title: 🔴 ContextOutlet en forma de tipo
|
||||
description: El desafío 4 se trata de tipificar de manera fuerte las directivas de ngContextOutlet
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
label: Reto
|
||||
number: 4
|
||||
challengeNumber: 4
|
||||
command: angular-context-outlet-type
|
||||
blogLink: https://medium.com/@thomas.laforge/ngtemplateoutlet-type-checking-5d2dcb07a2c6
|
||||
sidebar:
|
||||
|
||||
@@ -2,9 +2,7 @@
|
||||
title: 🟢 Aplicación CRUD
|
||||
description: El desafío 5 se trata de refactorizar una aplicación CRUD.
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
label: Reto
|
||||
number: 5
|
||||
challengeNumber: 5
|
||||
command: angular-crud
|
||||
sidebar:
|
||||
order: 2
|
||||
|
||||
@@ -2,9 +2,7 @@
|
||||
title: 🟠 Directiva Estructural
|
||||
description: El Desafío 6 se trata de generar una Directiva Estructural que manipule los permisos
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
label: Reto
|
||||
number: 6
|
||||
challengeNumber: 6
|
||||
command: angular-permissions
|
||||
blogLink: https://medium.com/@thomas.laforge/create-a-custom-structural-directive-to-manage-permissions-like-a-pro-11a1acad30ad
|
||||
sidebar:
|
||||
|
||||
@@ -2,9 +2,7 @@
|
||||
title: 🟠 Optimizar el Change Detection al desplazarse
|
||||
description: Desafío 12 sobre la optimización del número de ciclos de detección de cambios al desplazarse
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
label: Reto
|
||||
number: 12
|
||||
challengeNumber: 12
|
||||
command: performance-scroll-cd
|
||||
sidebar:
|
||||
order: 107
|
||||
|
||||
@@ -2,9 +2,7 @@
|
||||
title: 🟢 Default vs OnPush
|
||||
description: El desafío 34 trata sobre aprender la diferencia entre las estrategias de detección de cambios Default y OnPush.
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
label: Reto
|
||||
number: 34
|
||||
challengeNumber: 34
|
||||
command: performance-default-onpush
|
||||
sidebar:
|
||||
order: 7
|
||||
|
||||
@@ -2,9 +2,7 @@
|
||||
title: 🟢 Memoización
|
||||
description: El desafío 35 trata sobre cómo funcionan las tuberías puras
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
label: Reto
|
||||
number: 35
|
||||
challengeNumber: 35
|
||||
command: performance-memoized
|
||||
sidebar:
|
||||
order: 8
|
||||
|
||||
@@ -2,9 +2,7 @@
|
||||
title: 🟢 Optimización de NgFor
|
||||
description: El Desafío 36 trata sobre como funciona trackby
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
label: Reto
|
||||
number: 36
|
||||
challengeNumber: 36
|
||||
command: performance-ngfor-optimize
|
||||
sidebar:
|
||||
order: 13
|
||||
|
||||
@@ -2,9 +2,7 @@
|
||||
title: 🟠 Optimizando una lista larga
|
||||
description: El desafio 37 trata sobre como optimizar una lista grande de elementos
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
label: Reto
|
||||
number: 37
|
||||
challengeNumber: 37
|
||||
command: performance-ngfor-biglist
|
||||
sidebar:
|
||||
order: 117
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: 🟢 Projeção
|
||||
description: Desafio 1 é sobre aprender a projetar elementos DOM através de componentes
|
||||
author: thomas-laforge
|
||||
challenge:
|
||||
number: 1
|
||||
challengeNumber: 1
|
||||
command: angular-projection
|
||||
blogLink: https://medium.com/@thomas.laforge/create-a-highly-customizable-component-cc3a9805e4c5
|
||||
videoLink:
|
||||
|
||||
Reference in New Issue
Block a user