Weekly Update 113: Making Swift sing
This is a copy of our weekly newsletter for developers which you can subscribe to here.
Jag has been working hard at finding sources for information, measuring the coverage of existing Swift Instant Answers (see diagram below), and listing the kind of queries we'd like to cover — things like syntax searches (e.g.
swift forEach), error messages (e.g.
swift mkmapitem unknown location), and so on.
All of this analysis, with proposals for how to implement the improvements, are detailed in the Swift Search Overview topic. We welcome you to join in, whether it's getting stuck in with code or offering helpful suggestions.
For specific tasks, here are some that are currently looking for a contributor:
- Create SwiftDocs Instant Answer
The work has already started but can be taken over with lots of room for improvement.
- Apple Docs: Add redirects to the output file
We'd like searches such as "NSDate.compare" and "compare" to link to the same article.
- Apple Docs: Add disambiguations to the output file
We'd like multiple results to be displayed when more than one entry exists.
- Microsoft Powershell Cheat Sheet: Fix typo
An ideal first contribution, this is simply changing "CaseSenstitive" to "CaseSensitive".
- Visual Studio Cheat Sheet: Add more shortcuts
Apparently there are lots that could be added, and there's probably room for more than one person to contribute.
IAs for Adoption
The following Instant Answers are looking for a maintainer — someone to moderate suggested changes from the community as well as address any issues that pop up in the future. If you'd like to step forward, please create an issue on GitHub using the button at the bottom of each IA page.
We always recommend making a new Git branch (not master) for each Instant Answer or project you work on, but it's easy to forget. Sometimes we receive pull requests with an extra file also included by mistake. If that happens to you, and if the pull request is not yet merged, don't panic! Here's how to fix it...
Firstly, check what branch you're on and what files are being tracked or staged in Git. In fact, do this at the start of every Git session:
Study the output to make sure no other stray files are there, and to make sure you're on the right branch. Now you can remove the extra file (called "extra-file.json" in this example) from your local environment:
Then also remove it from Git:
git rm extra-file.json
Now make a new commit and add an explanatory message:
git commit -m "Removed extra file"
Finally, push this change (commit) to your open pull request:
git push origin [my-branch]
There you go. You're back to normal and can relax!
That's all for this week — have a great weekend.
- The DuckDuckGo Staff