Skip to content
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

Prototype methods, objects without __proto__ #195

Merged
merged 6 commits into from Jun 3, 2020
Merged

Prototype methods, objects without __proto__ #195

merged 6 commits into from Jun 3, 2020

Conversation

cortizg
Copy link
Contributor

@cortizg cortizg commented May 18, 2020

No description provided.

1-08-04-pm Corregido 14

1-08-04-pm Corregido 15
Copy link
Member

@joaquinelio joaquinelio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bien, sugiero el rearmado de algunas frases.

no se si se debe modificar
index.md (se usa como link, aunque también para mostrar menú)
los svg (y que no sé cómo probar desde acá) creo haber leído que se llaman con parámetros y no se debían modificar pero no pude encontrar dónde.

1-js/08-prototypes/04-prototype-methods/article.md Outdated Show resolved Hide resolved
1-js/08-prototypes/04-prototype-methods/article.md Outdated Show resolved Hide resolved
1-js/08-prototypes/04-prototype-methods/article.md Outdated Show resolved Hide resolved

```js
// fully identical shallow clone of obj
// clon superficial totalmente idéntico de obj
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no entiendo por qué puso shallow, es obj es simplemente "idéntico", nada más. salvo que signifique copia llana. no lo pondría. Tembién me molesta la redundancia del original, pero lo quiere sobresalir de la copia via loop que sí es superficial.

// clon totalmente idéntico de obj

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"shallow" es para identificar que no tiene objetos anidados en su interior

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

¡AAAGGH!
DISCULPEN la falta de atención. metí un err donde no lo había
Debería poner un PR al inglés, poque "idéntico" confunde,
hay obj copiados superficialmente (es CORRECTA la palabra) por lo tanto NO idénticos,
y obj copiados recursivamente , IDÉNTICO y no superficial , creí que se refería a esto

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

¿seria entonces: clon superficial totalmente idéntico a obj?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PFFF
si yo estuviera estudiando esto, abandonaría

quizas sea que la capa superficial sí es idéntica
(porque podrías copiar solo prop y metodos y dejar sin copiar el resto)

No me animo a corregir, tengo que repasar el tema. Haciendo pruebas.
@ezzep66 sí parece entenderlo

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fully identical >> totalmente idéntico
shallow clone >> clon superficial
of obj >> de obj

clon superficial de obj totalmente idéntico
me parece...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok: clon superficial de obj totalmente idéntico

1-js/08-prototypes/04-prototype-methods/article.md Outdated Show resolved Hide resolved

The built-in `__proto__` getter/setter is unsafe if we'd want to put user-generated keys in to an object. Just because a user may enter "__proto__" as the key, and there'll be an error with hopefully easy, but generally unpredictable consequences.
El getter/setter incorporado de `__proto__` no es seguro si queremos poner claves generadas por el usuario en un objeto. Aunque un usuario puede ingresar `"__proto __"` como clave, y habrá un error, con consecuencias levemente esperanzadoras, pero generalmente impredecibles.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

( ) , y habrá un error, con consecuencias, con esperanza tranquilas pero generalmente impredecibles.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yo diría
con consecuencias levemente fáciles, pero generalmente impredecibles.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

eehhhmm...
qué significa "levemente fácil". Definitiva y rotundamente y un completo CREO QUE NO :)

Uno pone el parche, potencialmente peligroso. entonces
"easy" acá no es "fácil" sino "suave" ("easy, boy" cuando tranquilizás al perro)
hopefully easy
"consecuencias que, esperamos, sean leves/imperceptibles/no dañinas."
"con suerte, consecuencias leves o nulas" menos literal

take it easy

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

se escucha mejor!

1-js/08-prototypes/04-prototype-methods/article.md Outdated Show resolved Hide resolved
1-js/08-prototypes/index.md Show resolved Hide resolved
@javascript-translate-bot

Please make the requested changes. After it, add a comment "/done".
Then I'll ask for a new review 👻

@cortizg
Copy link
Contributor Author

cortizg commented May 30, 2020

/done

Copy link
Member

@joaquinelio joaquinelio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ezzep66
"apruebo"
pero no me animo a "approve"
tengo miedo que haga un merge automático
¿seguimos alimentando el repo? ¿probamos, pongo approve y vemos si el bot hace merge?
porque todavía no sabemos como manejar el repo actual

Copy link
Contributor

@EzequielCaste EzequielCaste left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@EzequielCaste
Copy link
Contributor

1 change requested
@joaquinelio
joaquinelio requested changes

me queda colgado eso...

@joaquinelio
Copy link
Member

joaquinelio commented May 30, 2020

Aprobé sin leer jaja ¿está hecho? Lead this, @ezzep66 te dejo el merge porque en un punto me supera.
Siempre se puede corregir, si cabe.

el bot gerentea más de lo que pensaba,
el traductor debería poner comentario /done en lugar de "listo/ok", y el bot lo manda a rerevisar

@vplentinax vplentinax merged commit 39af0cc into javascript-tutorial:master Jun 3, 2020
@javascript-translate-bot

Thank you 💖 I updated the Progress Issue #17 🎉 🎉 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants