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

#281 improve some code smell & more #292

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

jonatan-lledo-netcentric
Copy link
Collaborator

@jonatan-lledo-netcentric jonatan-lledo-netcentric commented Feb 20, 2023

There is always room for improvement, but this is just one step to refactoring the current main scripts: scripts.js and lib-franklin.js (still a work in progress, but the current work can be added and retaken later to continue with the refactor)

Fix #281

Test URLs:

@jonatan-lledo-netcentric jonatan-lledo-netcentric linked an issue Feb 20, 2023 that may be closed by this pull request
@aem-code-sync
Copy link

aem-code-sync bot commented Feb 20, 2023

Hello, I'm Franklin Bot and I will run some test suites that validate the page speed.
In case there are problems, just click the checkbox below to rerun the respective action.

  • Re-run PSI Checks

@aem-code-sync
Copy link

aem-code-sync bot commented Feb 20, 2023

Page Score PSI Audit Google
/ SI FCP LCP TBT CLS PSI

@aem-code-sync
Copy link

aem-code-sync bot commented Oct 6, 2023

Hello, I'm the AEM Code Sync Bot and I will run some test suites that validate the page speed.
In case there are problems, just click the checkbox below to rerun the respective action.

  • Re-run PSI Checks

@aem-code-sync
Copy link

aem-code-sync bot commented Oct 6, 2023

Page Scores Audits Google
/ PERFORMANCE A11Y SEO BEST PRACTICES SI FCP LCP TBT CLS PSI

@jonatan-lledo-netcentric
Copy link
Collaborator Author

a colleague of my team reminded me that if Adobe updates lib-franklin, all changes in lib-franklin.js will be lost, so maybe it is better if in the changes that I made, we can revoke them, but not the ones in scripts.js, WDYT @tomasznetcentric

@tomasznetcentric
Copy link
Collaborator

a colleague of my team reminded me that if Adobe updates lib-franklin, all changes in lib-franklin.js will be lost, so maybe it is better if in the changes that I made, we can revoke them, but not the ones in scripts.js, WDYT @tomasznetcentric

@jonatan-lledo-netcentric but make this refactoring sense outside of the lib-franklin.js ?

@jonatan-lledo-netcentric
Copy link
Collaborator Author

a colleague of my team reminded me that if Adobe updates lib-franklin, all changes in lib-franklin.js will be lost, so maybe it is better if in the changes that I made, we can revoke them, but not the ones in scripts.js, WDYT @tomasznetcentric

@jonatan-lledo-netcentric but make this refactoring sense outside of the lib-franklin.js ?

not necessarily, at that moment was a matter of seeing if the code could be improved and I started with the core scripts. but currently, there are enough open issues to work with more important than this one. WDYT?

@nc-andreashaller
Copy link
Collaborator

a colleague of my team reminded me that if Adobe updates lib-franklin, all changes in lib-franklin.js will be lost, so maybe it is better if in the changes that I made, we can revoke them, but not the ones in scripts.js, WDYT @tomasznetcentric

@jonatan-lledo-netcentric but make this refactoring sense outside of the lib-franklin.js ?

not necessarily, at that moment was a matter of seeing if the code could be improved and I started with the core scripts. but currently, there are enough open issues to work with more important than this one. WDYT?

Just to clarify: lib-franklin.js will not be auto updated by Adobe, we always have to pull changes manually from the boilerplate if we want to update. Having that said we should avoid making changes which are not functional to minimise effort if we want to take over changes.

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

Successfully merging this pull request may close these issues.

Improve/refactor initial code
3 participants