Energiser
Every CYF session begins with an energiser. Usually there’s a rota showing who will lead the energiser. We have some CYF favourite games you can play if you are stuck.
- Traffic Jam: re-order the cars to unblock yourself
- Telephone: draw the words and write the pictures
- Popcorn show and tell: popcorn around the room and show one nearby object or something in your pocket or bag and explain what it means to you.
Teamwork Project S3 🔗
Learning Objectives
Preparation
Introduction
When mapping a product, we go from the high to the lowest level to plan our delivery. The reason for that is so that the team and stakeholders all have the same knowledge of the strategy of the product and the main end goal.
However, we cannot deliver everything at once. And we also cannot plan every detail. We can prioritise the must-haves and then focus on them.
Product > Features > User Stories > Tasks
This mapping process is also sometimes called User Journey mapping or Story Mapping. And you can - and should - do it whenever you are starting a new project.
What questions should we ask to identify what needs to be built?
🎯 Goal: To understand the requirements of building a library website. (5 minutes)
Let’s assume we have been asked to build a library website that allows you to borrow books.
- Discuss briefly as a class what questions we should ask to understand better what we will build.
- Write these questions on post-its and share them on the collaborative board.
Make sure to encourage different people to share their ideas
Focus is on the questions, not the answers!
What features should this website have?
🎯 Goal: To understand the process of breaking down a product into features. (10 minutes)
Let’s assume we got answers to all our questions about the product. (We are not going to actually answer them)
Overall, the goal is to build a website with a catalogue of books that can be borrowed online.
- In small groups, identify the main features you would expect to see on this website. In this example, features could be a shopping cart, book search, etc.
- One person of each group to share the group’s thoughts with the class.
Breaking features down into user stories
🎯 Goal: To understand the process of breaking down features into user stories. (15 minutes)
Now that we have all the features, we need to break them down into user stories.
In small groups, pick one of the features and break it down into at least 2 user stories. For example, for the shopping cart feature the user stories could be:
- As a library user, I want to be able to remove items I have included in my shopping cart so that when I checkout the remaining books are the ones I want to borrow.
- As a library user, I want to be able to pay with credit card for the books in my shopping cart so they can be delivered to me
Different group representatives volunteer to share thoughts with the class.
Tasks needed to deliver this user story
🎯 Goal: To understand the process of breaking down user stories into tasks and distributing those tasks among team members. (15 minutes)
Now that we have user stories, it is time to break them down into tasks. Tasks are used to break down user stories into smaller components that can then be assigned to individual team members.
Chose a user story and in the same groups complete the following:
Identify the tasks that need to be completed in order to deliver value to the user, providing the outcome described in the user story.
Identify relationships and dependencies between tasks.
- How does a change in Task A affect other tasks?
- Does Task A need to be completed before we can work on Task B?
Size those tasks taking into account complexity and dependencies.
Answer these questions: when is it the right time to assign tasks to team members, what would be the criteria you would follow when assigning tasks?
Examples of tasks for a user story describing the book search functionality could be Search Box, Text Autocomplete, Database creation and setup. Discuss in small groups.
Again, a different group representative volunteer to share thoughts with the class.
Morning Break
A quick break of fifteen minutes so we can all concentrate on the next piece of work.
Study Group
What are we doing now?
You’re going to use this time to work through coursework. Your cohort will collectively self-organise to work through the coursework together in your own way. Sort yourselves into groups that work for you.
Use this time wisely
You will have study time in almost every class day. Don’t waste it. Use it to:
- work through the coursework
- ask questions and get unblocked
- give and receive code review
- work on your portfolio
- develop your own projects
🛎️ Code waiting for review 🔗
Below are trainee coursework Pull Requests that need to be reviewed by volunteers.
Bump @babel/traverse from 7.21.4 to 7.23.2 🔗
Bumps @babel/traverse from 7.21.4 to 7.23.2.
Release notes
Sourced from @babel/traverse
's releases.
v7.23.2 (2023-10-11)
NOTE: This release also re-publishes
@babel/core
, even if it does not appear in the linked release commit.Thanks
@jimmydief
for your first PR!:bug: Bug Fix
babel-traverse
- #16033 Only evaluate own String/Number/Math methods (
@nicolo-ribaudo
)babel-preset-typescript
- #16022 Rewrite
.tsx
extension when usingrewriteImportExtensions
(@jimmydief
)babel-helpers
babel-helpers
,babel-plugin-transform-modules-commonjs
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
- #16025 Avoid override mistake in namespace imports (
@nicolo-ribaudo
)Committers: 5
- Babel Bot (
@babel-bot
)- Huáng Jùnliàng (
@JLHwung
)- James Diefenderfer (
@jimmydief
)- Nicolò Ribaudo (
@nicolo-ribaudo
)@liuxingbaoyu
v7.23.1 (2023-09-25)
Re-publishing
@babel/helpers
due to a publishing error in 7.23.0.v7.23.0 (2023-09-25)
Thanks
@lorenzoferre
and@RajShukla1
for your first PRs!:rocket: New Feature
babel-plugin-proposal-import-wasm-source
,babel-plugin-syntax-import-source
,babel-plugin-transform-dynamic-import
- #15870 Support transforming
import source
for wasm (@nicolo-ribaudo
)babel-helper-module-transforms
,babel-helpers
,babel-plugin-proposal-import-defer
,babel-plugin-syntax-import-defer
,babel-plugin-transform-modules-commonjs
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
,babel-standalone
- #15878 Implement
import defer
proposal transform support (@nicolo-ribaudo
)babel-generator
,babel-parser
,babel-types
- #15845 Implement
import defer
parsing support (@nicolo-ribaudo
)- #15829 Add parsing support for the "source phase imports" proposal (
@nicolo-ribaudo
)babel-generator
,babel-helper-module-transforms
,babel-parser
,babel-plugin-transform-dynamic-import
,babel-plugin-transform-modules-amd
,babel-plugin-transform-modules-commonjs
,babel-plugin-transform-modules-systemjs
,babel-traverse
,babel-types
babel-standalone
babel-helper-function-name
,babel-helper-member-expression-to-functions
,babel-helpers
,babel-parser
,babel-plugin-proposal-destructuring-private
,babel-plugin-proposal-optional-chaining-assign
,babel-plugin-syntax-optional-chaining-assign
,babel-plugin-transform-destructuring
,babel-plugin-transform-optional-chaining
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
,babel-standalone
,babel-types
- #15751 Add support for optional chain in assignments (
@nicolo-ribaudo
)babel-helpers
,babel-plugin-proposal-decorators
- #15895 Implement the "decorator metadata" proposal (
@nicolo-ribaudo
)babel-traverse
,babel-types
- #15893 Add
t.buildUndefinedNode
(@liuxingbaoyu
)babel-preset-typescript
... (truncated)
Changelog
Sourced from @babel/traverse
's changelog.
v7.23.2 (2023-10-11)
:bug: Bug Fix
babel-traverse
- #16033 Only evaluate own String/Number/Math methods (
@nicolo-ribaudo
)babel-preset-typescript
- #16022 Rewrite
.tsx
extension when usingrewriteImportExtensions
(@jimmydief
)babel-helpers
babel-helpers
,babel-plugin-transform-modules-commonjs
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
- #16025 Avoid override mistake in namespace imports (
@nicolo-ribaudo
)v7.23.0 (2023-09-25)
:rocket: New Feature
babel-plugin-proposal-import-wasm-source
,babel-plugin-syntax-import-source
,babel-plugin-transform-dynamic-import
- #15870 Support transforming
import source
for wasm (@nicolo-ribaudo
)babel-helper-module-transforms
,babel-helpers
,babel-plugin-proposal-import-defer
,babel-plugin-syntax-import-defer
,babel-plugin-transform-modules-commonjs
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
,babel-standalone
- #15878 Implement
import defer
proposal transform support (@nicolo-ribaudo
)babel-generator
,babel-parser
,babel-types
- #15845 Implement
import defer
parsing support (@nicolo-ribaudo
)- #15829 Add parsing support for the "source phase imports" proposal (
@nicolo-ribaudo
)babel-generator
,babel-helper-module-transforms
,babel-parser
,babel-plugin-transform-dynamic-import
,babel-plugin-transform-modules-amd
,babel-plugin-transform-modules-commonjs
,babel-plugin-transform-modules-systemjs
,babel-traverse
,babel-types
babel-standalone
babel-helper-function-name
,babel-helper-member-expression-to-functions
,babel-helpers
,babel-parser
,babel-plugin-proposal-destructuring-private
,babel-plugin-proposal-optional-chaining-assign
,babel-plugin-syntax-optional-chaining-assign
,babel-plugin-transform-destructuring
,babel-plugin-transform-optional-chaining
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
,babel-standalone
,babel-types
- #15751 Add support for optional chain in assignments (
@nicolo-ribaudo
)babel-helpers
,babel-plugin-proposal-decorators
- #15895 Implement the "decorator metadata" proposal (
@nicolo-ribaudo
)babel-traverse
,babel-types
- #15893 Add
t.buildUndefinedNode
(@liuxingbaoyu
)babel-preset-typescript
- #15913 Add
rewriteImportExtensions
option to TS preset (@nicolo-ribaudo
)babel-parser
- #15896 Allow TS tuples to have both labeled and unlabeled elements (
@yukukotani
):bug: Bug Fix
babel-plugin-transform-block-scoping
- #15962 fix:
transform-block-scoping
captures the variables of the method in the loop (@liuxingbaoyu
):nail_care: Polish
babel-traverse
- #15797 Expand evaluation of global built-ins in
@babel/traverse
(@lorenzoferre
)babel-plugin-proposal-explicit-resource-management
- #15985 Improve source maps for blocks with
using
declarations (@nicolo-ribaudo
):microscope: Output optimization
babel-core
,babel-helper-module-transforms
,babel-plugin-transform-async-to-generator
,babel-plugin-transform-classes
,babel-plugin-transform-dynamic-import
,babel-plugin-transform-function-name
,babel-plugin-transform-modules-amd
,babel-plugin-transform-modules-commonjs
,babel-plugin-transform-modules-umd
,babel-plugin-transform-parameters
,babel-plugin-transform-react-constant-elements
,babel-plugin-transform-react-inline-elements
,babel-plugin-transform-runtime
,babel-plugin-transform-typescript
,babel-preset-env
- #15984 Inline
exports.XXX =
update in simple variable declarations (@nicolo-ribaudo
)v7.22.20 (2023-09-16)
... (truncated)
Commits
b4b9942
v7.23.2b13376b
Only evaluate own String/Number/Math methods (#16033)ca58ec1
v7.23.00f333da
AddcreateImportExpressions
parser option (#15682)3744545
Fix lintingc7e6806
Addt.buildUndefinedNode
(#15893)38ee8b4
Expand evaluation of global built-ins in@babel/traverse
(#15797)9f3dfd9
v7.22.203ed28b2
Fully support||
and&&
inpluginToggleBooleanFlag
(#15961)77b0d73
v7.22.19- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don’t alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.
London 10 - Paulina Wywrot - Unit Testing - JS3 - Week 4 🔗
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Start a reviewLondon 10 - Paulina Wywrot - Using Fetch - JS3 - Week 2 🔗
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Start a reviewLondon 10 - Paulina Wywrot - Programmer-Humour - JS3 - Week 3 🔗
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Start a reviewLondon_10 | Andrius Isin | using-fetch | JS3 | Week 3 🔗
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Start a reviewCommunity Lunch
Every Saturday at CYF we cook and eat together. We share our food and our stories. We learn about each other and the world. We build community.
This is everyone’s responsibility, so help with what is needed to make this happen, for example, organising the food, setting up the table, washing up, tidying up, etc. You can do something different every week. You don’t need to be constantly responsible for the same task.
Break down 🔗
Debugging is Asking Questions
Prep
- Re-read this article about Mental Models
- Watch this video about VSCode Debugger and follow along with the mini-workshop
- Open this CYF Workshops repo in VSCode and go to the
debugging/bank
folder to find the problem bank.
Whew, that’s loads! But we did set it all as coursework, so you have done it already, right? 😉
Today we’re going to use our formal language of developer questions. We began with this basic format:
- What I did
- What I expected
- What actually happened
This format helps to find the discrepancies between expectations and reality. (This is the gap in our understanding.)
It really helps us with debugging. Today we will use a debugger and our scientific method to find and fix bugs. Recall your scientific method:
Recap asking questions
Predict & Explain
- Make a prediction by explaining what the outcome will be
Test
- Run the code to see what actually happens
Compare and Update
- Compare the outcome with our prediction
- Explain the gap between our prediction and what actually happened
- Update our understanding
This process is cyclical.
graph LR A[Predict] B[Explain] C[Test] D[Compare] E[Update] A --> B B --> C C --> D D --> E E --> A
Setup
Get into pairs. Each pair consists of two roles:
- Computer: Execute the code mentally, predicting the outcome.
- Debugger: Use the VSCode debugger to step through the code.
You will swap roles after each exercise.
Set a whole class timer for 10 minutes.
Stepping
Understanding Variables and Flow, 10m
Identify the value of variables at each step in a loop.
const sumArray = (numbers) => {
let total = 0;
for (let i = 0; i < numbers.length; i++) {
total += numbers[i];
}
return total;
};
console.log(sumArray([1, 2, 3]));
Computer:
- Write down predictions for
total
andi
values before each loop iteration. - Compare predictions after each Debugger’s step.
Debugger:
- Open
sumArray.js
in VSCode. - Choose ‘Run > Start Debugging’ from the menu.
- Set a breakpoint at
total += numbers[i];
. - Step into your function.
- Step Over through iteration until your loop is complete.
- Monitor
total
andi
in the Variables section.
Debugging
Okay, swap roles. Set a whole class timer for 15 minutes.
Finding an Error, 15m
const findLargest = (numbers) => {
let largest = numbers[0];
for (let i = 1; i < numbers.length; i++) {
if (numbers[i] > largest) {
largest = numbers[i];
}
}
return largest;
};
console.log(findLargest([3, 7, 2, 5, 6]));
Debugger:
- Open
findLargest
in VSCode. - Predict the return value of
findLargest
. Write your prediction down. - Set a breakpoint at
if (numbers[i] > largest)
. - Debug and inspect
i
,numbers[i]
, andlargest
. - Write down the return value of
findLargest([3, 7, 2, 5, 6])
.
Computer:
- Predict the value of
largest
after each loop iteration. - ‘Execute’ the code and write down the actual value of
largest
after each loop iteration. - Write down the return value of
findLargest([3, 7, 2, 5, 6])
. - Now execute the code in VSCode. Did you get the same result?
Both (briefly) write up your mental model using this format:
- What I did
- What I expected. Make sure you include your prediction here
- What actually happened
Okay, swap roles. If you have time left and you’re into this, there are many problems stored in debugging/bank
. Set a whole class timer for 15 minutes.
Problem Bank, 30m
Pick any problem from the bank and work through it together. Use the debugger and the scientific method to find and fix the bug.
Write up your findings in the developer question format. Swap roles and repeat until we run out of time.
🧑🏾💻🙋 Developer questions contain
- 🔗 Links 👍
- Objectives - what are you actually trying to do? 👍
- 🖼️ Screenshots of UI 👍
- 📝
Code blocks
👍 - 📷
Screenshots of code🙅
📚 Further reading
Study Group
What are we doing now?
You’re going to use this time to work through coursework. Your cohort will collectively self-organise to work through the coursework together in your own way. Sort yourselves into groups that work for you.
Use this time wisely
You will have study time in almost every class day. Don’t waste it. Use it to:
- work through the coursework
- ask questions and get unblocked
- give and receive code review
- work on your portfolio
- develop your own projects
Afternoon Break
Please feel comfortable and welcome to pray at this time if this is part of your religion.
If you are breastfeeding and would like a private space, please let us know.
Study Group
What are we doing now?
You’re going to use this time to work through coursework. Your cohort will collectively self-organise to work through the coursework together in your own way. Sort yourselves into groups that work for you.
Use this time wisely
You will have study time in almost every class day. Don’t waste it. Use it to:
- work through the coursework
- ask questions and get unblocked
- give and receive code review
- work on your portfolio
- develop your own projects
🛎️ Code waiting for review 🔗
Below are trainee coursework Pull Requests that need to be reviewed by volunteers.
Bump @babel/traverse from 7.21.4 to 7.23.2 🔗
Bumps @babel/traverse from 7.21.4 to 7.23.2.
Release notes
Sourced from @babel/traverse
's releases.
v7.23.2 (2023-10-11)
NOTE: This release also re-publishes
@babel/core
, even if it does not appear in the linked release commit.Thanks
@jimmydief
for your first PR!:bug: Bug Fix
babel-traverse
- #16033 Only evaluate own String/Number/Math methods (
@nicolo-ribaudo
)babel-preset-typescript
- #16022 Rewrite
.tsx
extension when usingrewriteImportExtensions
(@jimmydief
)babel-helpers
babel-helpers
,babel-plugin-transform-modules-commonjs
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
- #16025 Avoid override mistake in namespace imports (
@nicolo-ribaudo
)Committers: 5
- Babel Bot (
@babel-bot
)- Huáng Jùnliàng (
@JLHwung
)- James Diefenderfer (
@jimmydief
)- Nicolò Ribaudo (
@nicolo-ribaudo
)@liuxingbaoyu
v7.23.1 (2023-09-25)
Re-publishing
@babel/helpers
due to a publishing error in 7.23.0.v7.23.0 (2023-09-25)
Thanks
@lorenzoferre
and@RajShukla1
for your first PRs!:rocket: New Feature
babel-plugin-proposal-import-wasm-source
,babel-plugin-syntax-import-source
,babel-plugin-transform-dynamic-import
- #15870 Support transforming
import source
for wasm (@nicolo-ribaudo
)babel-helper-module-transforms
,babel-helpers
,babel-plugin-proposal-import-defer
,babel-plugin-syntax-import-defer
,babel-plugin-transform-modules-commonjs
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
,babel-standalone
- #15878 Implement
import defer
proposal transform support (@nicolo-ribaudo
)babel-generator
,babel-parser
,babel-types
- #15845 Implement
import defer
parsing support (@nicolo-ribaudo
)- #15829 Add parsing support for the "source phase imports" proposal (
@nicolo-ribaudo
)babel-generator
,babel-helper-module-transforms
,babel-parser
,babel-plugin-transform-dynamic-import
,babel-plugin-transform-modules-amd
,babel-plugin-transform-modules-commonjs
,babel-plugin-transform-modules-systemjs
,babel-traverse
,babel-types
babel-standalone
babel-helper-function-name
,babel-helper-member-expression-to-functions
,babel-helpers
,babel-parser
,babel-plugin-proposal-destructuring-private
,babel-plugin-proposal-optional-chaining-assign
,babel-plugin-syntax-optional-chaining-assign
,babel-plugin-transform-destructuring
,babel-plugin-transform-optional-chaining
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
,babel-standalone
,babel-types
- #15751 Add support for optional chain in assignments (
@nicolo-ribaudo
)babel-helpers
,babel-plugin-proposal-decorators
- #15895 Implement the "decorator metadata" proposal (
@nicolo-ribaudo
)babel-traverse
,babel-types
- #15893 Add
t.buildUndefinedNode
(@liuxingbaoyu
)babel-preset-typescript
... (truncated)
Changelog
Sourced from @babel/traverse
's changelog.
v7.23.2 (2023-10-11)
:bug: Bug Fix
babel-traverse
- #16033 Only evaluate own String/Number/Math methods (
@nicolo-ribaudo
)babel-preset-typescript
- #16022 Rewrite
.tsx
extension when usingrewriteImportExtensions
(@jimmydief
)babel-helpers
babel-helpers
,babel-plugin-transform-modules-commonjs
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
- #16025 Avoid override mistake in namespace imports (
@nicolo-ribaudo
)v7.23.0 (2023-09-25)
:rocket: New Feature
babel-plugin-proposal-import-wasm-source
,babel-plugin-syntax-import-source
,babel-plugin-transform-dynamic-import
- #15870 Support transforming
import source
for wasm (@nicolo-ribaudo
)babel-helper-module-transforms
,babel-helpers
,babel-plugin-proposal-import-defer
,babel-plugin-syntax-import-defer
,babel-plugin-transform-modules-commonjs
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
,babel-standalone
- #15878 Implement
import defer
proposal transform support (@nicolo-ribaudo
)babel-generator
,babel-parser
,babel-types
- #15845 Implement
import defer
parsing support (@nicolo-ribaudo
)- #15829 Add parsing support for the "source phase imports" proposal (
@nicolo-ribaudo
)babel-generator
,babel-helper-module-transforms
,babel-parser
,babel-plugin-transform-dynamic-import
,babel-plugin-transform-modules-amd
,babel-plugin-transform-modules-commonjs
,babel-plugin-transform-modules-systemjs
,babel-traverse
,babel-types
babel-standalone
babel-helper-function-name
,babel-helper-member-expression-to-functions
,babel-helpers
,babel-parser
,babel-plugin-proposal-destructuring-private
,babel-plugin-proposal-optional-chaining-assign
,babel-plugin-syntax-optional-chaining-assign
,babel-plugin-transform-destructuring
,babel-plugin-transform-optional-chaining
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
,babel-standalone
,babel-types
- #15751 Add support for optional chain in assignments (
@nicolo-ribaudo
)babel-helpers
,babel-plugin-proposal-decorators
- #15895 Implement the "decorator metadata" proposal (
@nicolo-ribaudo
)babel-traverse
,babel-types
- #15893 Add
t.buildUndefinedNode
(@liuxingbaoyu
)babel-preset-typescript
- #15913 Add
rewriteImportExtensions
option to TS preset (@nicolo-ribaudo
)babel-parser
- #15896 Allow TS tuples to have both labeled and unlabeled elements (
@yukukotani
):bug: Bug Fix
babel-plugin-transform-block-scoping
- #15962 fix:
transform-block-scoping
captures the variables of the method in the loop (@liuxingbaoyu
):nail_care: Polish
babel-traverse
- #15797 Expand evaluation of global built-ins in
@babel/traverse
(@lorenzoferre
)babel-plugin-proposal-explicit-resource-management
- #15985 Improve source maps for blocks with
using
declarations (@nicolo-ribaudo
):microscope: Output optimization
babel-core
,babel-helper-module-transforms
,babel-plugin-transform-async-to-generator
,babel-plugin-transform-classes
,babel-plugin-transform-dynamic-import
,babel-plugin-transform-function-name
,babel-plugin-transform-modules-amd
,babel-plugin-transform-modules-commonjs
,babel-plugin-transform-modules-umd
,babel-plugin-transform-parameters
,babel-plugin-transform-react-constant-elements
,babel-plugin-transform-react-inline-elements
,babel-plugin-transform-runtime
,babel-plugin-transform-typescript
,babel-preset-env
- #15984 Inline
exports.XXX =
update in simple variable declarations (@nicolo-ribaudo
)v7.22.20 (2023-09-16)
... (truncated)
Commits
b4b9942
v7.23.2b13376b
Only evaluate own String/Number/Math methods (#16033)ca58ec1
v7.23.00f333da
AddcreateImportExpressions
parser option (#15682)3744545
Fix lintingc7e6806
Addt.buildUndefinedNode
(#15893)38ee8b4
Expand evaluation of global built-ins in@babel/traverse
(#15797)9f3dfd9
v7.22.203ed28b2
Fully support||
and&&
inpluginToggleBooleanFlag
(#15961)77b0d73
v7.22.19- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don’t alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.
London 10 - Paulina Wywrot - Unit Testing - JS3 - Week 4 🔗
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Start a reviewLondon 10 - Paulina Wywrot - Using Fetch - JS3 - Week 2 🔗
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Start a reviewLondon 10 - Paulina Wywrot - Programmer-Humour - JS3 - Week 3 🔗
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Start a reviewLondon_10 | Andrius Isin | using-fetch | JS3 | Week 3 🔗
Learners, PR Template
Self checklist
- I have committed my files one by one, on purpose, and for a reason
- I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
- I have tested my changes
- My changes follow the style guide
- My changes meet the requirements of this task
Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.
Start a reviewRetro: Start / Stop / Continue
Retro (20 minutes)
A retro is a chance to reflect on this past sprint. You can do this on a Jamboard (make sure someone clicks “Make a copy” before you start, and you work on that together) or on sticky notes on a wall.
- Set a timer for 5 minutes.
- Write down as many things as you can think of that you’d like to start, stop, and continue doing next sprint.
- Write one point per note and keep it short.
- When the timer goes off, one person should set a timer for 1 minute and group the notes into themes.
- Next, set a timer for 2 minutes and all vote on the most important themes by adding a dot or a +1 to the note.
- Finally, set a timer for 8 minutes and all discuss the top three themes.