Today, I want to tell you about the hiccups in moving from infinite scroll paging pattern to forward and back buttons.
I have various HTTP services that fetch data from the server.
I have a single paging component that I want to use in a number of views.
Therefore, I need a way to inject different services into my paging component for the fetchData() function to use.
I have a directive defining a component that is reused in a number of views.
I have a view in my app that needs 2 instances of this component. I also need the two instances to be in sync and behave as one.*
What is SquareSpace?
Squarespace is a content management system that enables users with little to no technical experience easily build, manage and host a website or blog.
If the default templates and behavior isn’t quite what you’re looking for, the platform offers “Developer Mode.” Turning this mode on for your site allows you to write custom templates and code snippets to modify your site’s default look, feel and behavior.
Tip: If you turn OFF developer mode, all that custom code disappears into the aether. More about that here.
Why run locally?
As anyone with development experience knows, changes don’t always look or behave as planned and bugs happen. To remove the risk of deploying a change that could break your site (or your client’s site) during the development process, it’s great practice to develop those changes locally, test them, and then push them to your live site once you’re sure they’re production ready.
A quick blurb on a nifty feature I came across today in the Swift Programming Language Guide:
I guard against invalid values ALL the time with a nice little if/else statement upon entering a block of code, but here swift has made an even more readable keyword to highlight the behavior: guard