TEAM LICENSES: Save money and learn new skills through a Hacking with Swift+ team license >>

Ultimate Portfolio App: Documenting our Code - Workaround tag suggestion

Forums > Videos

I find it beneficial to tag the sections of code that are workarounds. Later on, after a code platform change, it is easy to search through all the source code for the workaround code sections, and to review them for removal or amendment. I keep the workaround tag in the comment until no longer needed.

At start of a comment line, I use :workaround:

example:

// :workaround: . . .

You could use whatever tag you want, as long as it is not used for, or could be confused with anything else.

Hopefully, you may find doing this of benefit too.

5      

Hacking with Swift is sponsored by Superwall.

SPONSORED Superwall lets you build & test paywalls without shipping updates. Run experiments, offer sales, segment users, update locked features and more at the click of button. Best part? It's FREE for up to 250 conversions / mo and the Superwall team builds out 100% custom paywalls – free of charge.

Learn More

Sponsor Hacking with Swift and reach the world's largest Swift community!

Archived topic

This topic has been closed due to inactivity, so you can't reply. Please create a new topic if you need to.

All interactions here are governed by our code of conduct.

 
Unknown user

You are not logged in

Log in or create account
 

Link copied to your pasteboard.