Messagekit: Update copyright dates to 2018

[SD10]

Need to change this in LICENSE.md & all the source files

-- Copyright (c) 2017 MessageKit
++ Copyright (c) 2017 - 2018 MessageKit

[SD10]

@richgabrielli Maybe you'd like to take a shot at this one too? There are a lot more dates to change on this one! The ChatExample project, the MessageKit project, and LICENSE.md

[Sherlouk]

I mentioned ages ago about defining a copyright template and including it in the project, not sure if someone looked into it before but if it was that'll need updating too!

(If it wasn't, maybe another case to reconsider so this can be the same for new files!)

[SD10]

@Sherlouk I’m so pleased that you’re offering to look into this for me!

_{Sent with GitHawk}

[Sherlouk]

Tad busy at the moment! But if anyone wants to:
https://oleb.net/blog/2017/07/xcode-9-text-macros/

[richgabrielli]

Should I update the year first (brute force) and then have this as another issue that needs to be looked at or combine both?

[Sherlouk]

FWIW as well, because I don't want someone brute forcing this. If you just use a simple command line you can replace it all in one swoop! Here's the command:

find . -name "*.swift" -exec sed -i '' "s/Copyright (c) 2017 MessageKit/Copyright (c) 2017-2018 MessageKit/g" {} \;

If you run this from the root directory, this will find all the files with the name wildcard .swift (aka all the swift files). It will then execute the provided command with the file name as a parameter.

Using sed we can find and replace the content of the files! It uses "/" as a delimiter so you can see the before and after phases!

Hopefully this'll help next year when you need to do the same thing!

@richgabrielli @SD10

[richgabrielli]

I will do this. I will do a few the brute force method so I can peruse some of the files and then research / try out the script. Thanks!

[richgabrielli]

Couple questions: I have changed the example project to my info so I could run. Did I mess up the project to submit a pull request?

[richgabrielli]

2nd question: found an error in Avatar.playground. Should I just leave it?

[SD10]

@richgabrielli I didn’t even know we had that playground still. You can leave it.

As for building the project, don’t worry about it. We’re not making code changes so I’m not concerned about CI.

If you made some changes to the .xcproj, etc, you can always discard the changes with a git checkout [file]

_{Sent with GitHawk}

[SD10]

As for the project template that can be a separate issue

_{Sent with GitHawk}

[richgabrielli]

lol. I will leave the playground.

I wanted to run the example, so I added my developer ID and did the recommended Xcode changes. Sorry. Should I delete and refork and not mess with it?

[richgabrielli]

And I had to run pod update in the Example directory.

[SD10]

🤔 You don’t need to refork. Just submit a PR and I’ll take a look. Make sure you check the box that allows me to edit the PR just in case.

_{Sent with GitHawk}

[SD10]

Closed by #439