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.

Sign up for GitHub

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

Jump to bottom

Add separation of concern #1429

Closed
wants to merge 1 commit into from
Closed

Add separation of concern #1429

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions learning-objectives/data.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,6 +131,7 @@ firebase:
front-end-web-dev:
- components
- state
- separation of concerns
Copy link
Contributor

Choose a reason for hiding this comment

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

separation-of-concerns para yml
Me gustaría escuchar que opinan otros en eso - específicamente cómo evaluamos en un project feedback o test.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
- separation of concerns
- separation-of-concerns

Ese pequeño cambio nomas habría que hacerle, pero además habría que agregar a los archivos de internacionalización de OAs un título y (ojalá) un link que explique el concepto, tanto en ES como PT!

Con eso estamos 😏

¡Mil gracias @icarito y @Freihart512 ! 🥳

# - routing

angular:
Expand Down