denrique-alvarez
commented
2 years ago - [x] 🥚 event-driven programming: identify the concept in a JS program via listeners & handlers
- [x] 🥚 entry points: describe what an entry point is, there are 2 kinds in the programs for this module - initialization & interaction. identify them in a program
- [x] 🥚 function roles: describe what function roles are and why they're important. they can identify a function's role given checklists for each role covered in this module:
- [x] 🥚 listeners: functions that attach event listeners to the DOM
- [x] 🥚 handlers: entry point for user interactions
- [x] 🥚 utils (utilities): pure functions to help do things with data
- [x] 🐣 components: render data into DOM elements to display for the user
- [ ] 🐥 custom events: create custom events in your components, passing useful data between components and handle
- [x] 🥚 DOM access: You read and write values from the DOM in an event handler
- [ ] 🥚 es5 vs. es6: You can demonstrate the change in developer-experience pre and post es6 by stepping through in the debugger and explaining differences in scoping (global vs. script, block vs. local, modules) between two programs with identical user experience but different implementations.
- [ ] 🥚 Scope Hierarchy: You are comfortable navigating different scopes in the browser's debugger to understand an existing application (script, module, closure, local, block)
- [x] 🥚 Code Splitting: You can ES Modules to split your code into multiple files & folders according to function role, data, listeners and initialization. They can use generated dependency diagrams and documentation to understand and navigate this folder structure.
- [x] 🥚 Dependency Graphs: You can use a project's dependency graph to understand how it is organized and to navigate the source code.
- [ ] 🥚 Development Strategies: You can write development strategies that have all of the program's data defined at the beginning, and separate each user story into interface and interaction tasks.
- [ ] 🐣 Naming Functions: You can come up with clear and helpful names for the functions in your program. A good function name will take into account the function's role and the program's domain, like in the /naming-variables exercises from Debugging.
- [ ] 🐣 DOM manipulation: You can manipulate the DOM when implementing level-appropriate user interactions
- [ ] 🐣 Isolating Components: You can use a test.html file to render your components with different inputs
- [ ] 🐣 Forms: You can do basic handling of form data via event.target.form
- [ ] 🐣 Handling events: You can use the event argument to process user interactions, including bubbled events using event.target
- [ ] 🐣 Passing Component Unit Tests: You can write vanilla DOM component functions to pass provided unit tests
- [ ] 🐣 refactoring: refactor a single-script tutorial-style web page into multiple files using imports and exports
- [ ] 🐥 reverse-engineering: You can incrementally reverse-engineer a level-appropriate user interaction following these steps: ui -> listener -> handler (-> logic and/or -> component)
- [ ] 🐔 From Spec: given user stories, You can develop a site from scratch using a template repository.
- [ ] 🐔 Writing Component Unit Tests: You can write unit tests to validate your component functions using BDD syntax
gelilaa
colevandersWands