6 Aug

Weekly Update 113: Making Swift sing

This is a copy of our weekly newsletter for developers which you can subscribe to here.

Hello contributors,

Firstly, thank you to everyone who's been visiting the new DuckDuckHack forum and joining in the discussions and brainstorming. We've been sharing analysis and todo items for improving programming Instant Answers and we're getting results! There are already merged and soon-to-be-merged pull requests for our five target languages: CSS, JavaScript, Perl, Python and Swift. This week, I'd like to draw your attention to the last of those — Swift.

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.

Diagram showing coverage of Swift queries

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:

Weekend Warriors

More high priority fix ideas here...

5-minute Fixes

More quick fix ideas here...

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.

Quick Tip

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:

git status

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:

rm extra-file.json

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

4 Tweet

This blog has been archived

Thank you for reading and contributing lively discussion to our blog! Read more posts about online privacy on our new blog at spreadprivacy.com.

it's great that the updates arrive faster

posted by gregoire5 • 1 year and 5 months ago Link

All updates are already operational?

posted by quentin25 • 1 year and 5 months ago Link

Awesome! The more programming languages you allow people to use, the broader of an audience you'll get.

posted by Hermida • 1 year and 5 months ago Link

This comment has been deleted.

posted by <hidden> • 1 year and 5 months ago Link