const obj = {};
let value = 0;
Object.defineProperty(obj, 'prop', {
get() {
return value;
},
set(newValue) {
value = newValue + 1;
},
configurable: true,
enumerable: true
});
obj.prop = 10;
console.log(obj.prop);
🔴What will be the output??
#javascript #quiz
👍11
const obj = { a: 1, b: 2 };
const proxy = new Proxy(obj, {
get(target, prop) {
return prop in target ? target[prop] : 0;
}
});
console.log(proxy.a, proxy.b, proxy.c);
💡 What will be output??
👏8👍2
⌨️ CSS: Align Icon with Text
"cap" is a CSS unit which is equal to the "cap height", that is, the size of the capital letters in a font.
This helps us to easily size icons that lie next to a piece of text to perfectly match the height of the text - no more fiddling around with rem or px units 🤩
❓ Question: Do you feel this is a better approach or do you like to define a specific dimension for your items?
"cap" is a CSS unit which is equal to the "cap height", that is, the size of the capital letters in a font.
This helps us to easily size icons that lie next to a piece of text to perfectly match the height of the text - no more fiddling around with rem or px units 🤩
❓ Question: Do you feel this is a better approach or do you like to define a specific dimension for your items?
👍21
🖥 Git: Merging vs Rebasing
In git, when there are some changes in a parent branch from which you forked, there are two strategies to incorporate them into your working branch:
✨ Merging:
As the name suggests, 'merges' the parent branch into your branch. The advantage is that handling conflicts (if any) is easier, since you only need to resolve them for the merge commit once. However, this may make the git history a bit harder to follow
✨ Rebasing:
Takes all the commits you made in your branch, and applies them on top of the head of the parent branch. As if repositioning the base of the branch.
This helps to create a linear and easy to follow git history, but conflict resolution may be tedious and you need to force push the branch to the origin.
In git, when there are some changes in a parent branch from which you forked, there are two strategies to incorporate them into your working branch:
✨ Merging:
As the name suggests, 'merges' the parent branch into your branch. The advantage is that handling conflicts (if any) is easier, since you only need to resolve them for the merge commit once. However, this may make the git history a bit harder to follow
✨ Rebasing:
Takes all the commits you made in your branch, and applies them on top of the head of the parent branch. As if repositioning the base of the branch.
This helps to create a linear and easy to follow git history, but conflict resolution may be tedious and you need to force push the branch to the origin.
👍6❤3
CHALLENGE
🔴 What will be the output?? Comment below 👇
const func = () => arguments.length;
console.log(func(1, 2, 3));
🔴 What will be the output?? Comment below 👇
👎4👍2🔥1
CHALLENGE
🔴What will be output??
const obj1 = { a: 1, b: { c: 2 } };
const obj2 = { ...obj1 };
obj1.b.c = 3;
console.log(obj2.b.c);
🔴What will be output??
❤7👍7
CHALLENGE
🔴 What will be the output??
class Parent {
static greet() {
return 'Hello from Parent';
}
}
class Child extends Parent {
static greet() {
return super.greet() + ' and Child';
}
}
const childInstance = new Child();
console.log(childInstance.greet);
🔴 What will be the output??
👍17👎5❤2