oleksiyrudenko / a-tiny-js-world Goto Github PK

Fix link to 'A guide to prototype-based class inheritance in JavaScript'

... so students are forced to list props explicitly for output and avoid Object methods.

E.g.:

• secretName for all inhabitants, non-printable,
• lastName for all humans, non-printable,
• apes/humans have legs and hands while other mammals would have paws

E.g. #50 can be a next level as well as a CatWoman, friends.

Current situation: friends are optional feature

Target situation:

• friends are a mandatory feature
• addFriends adds friends, skips duplicates
• a next level in the task completion journey (?)

This project needs an emblem.
Anything like the one in the bottom would fit.

Please, share your own artwork or refer to someone who could be of help. Permission to use the asset in non-commercial open source projects is required.

What the asset owner will get:

• credits with a link to her or his web site
• distribution of credits across forks of this project (not many yet though)

Thank you!

Embedded image link source: http://www.tactus.com/blog/create-amazing-360-degree-tiny-planet-photos-videos/

• MDN / super
• “Super” and “Extends” In JavaScript ES6 - Understanding The Tough Parts
• https://css-tricks.com/what-is-super-in-javascript/

Test level 1 (literal objects)

Requires exported functions with pre-defined signatures to

1. create general object presentation for required
2. create presentation of props that are not required for item 1

Have at least 2 predefined objects that use different order of keys.

Require particular order of props and each prop tagged like `legs: xx; `

Test level 2 (classes)

Requires all classes exported. Uses Inhabitant, Dog, Cat, Human.

Requires properties (legs, hands, paws, name, species, breed, friends, gender -- as per pets vs humans)

Set of "silent" props is assigned randomly per student. Silents some are for humans, other for pets, and shared. Props are tested as well.

Classes are expected to have methods:

• toString (general presentation)
• hasTail (all classes; humans shouldn't have tail prop)
• getBreed (only pets)
• getFriends (returns array)

Integrity checks

Test cases and pre-defined code (except for implementation templates) should not be changed. Checksums? No commit intervening into those files?