DEV Community: Dmytro Pylypenko

What’s New in Xcode 11.4?

Dmytro Pylypenko — Mon, 30 Mar 2020 08:30:40 +0000

Apple continuously tries and makes our favourite tool for developing applications for iOS/macOS/watchOS/etc. even better.

They announced interesting new features, which I’ll describe briefly. In my opinion, they’re actually very important.

Clang Compiler (11.0.3)
If your framework uses any third-party framework dependencies, the compiler displays the warning -Watimport-in-framework-header by default in the event of a framework importing a third-party dependency.

Debugging
The view debugger shows UILayoutGuide and its referencing constraints
The view debugger supports showing layers.
Editor → Show Layers
You can forward Xcode’s Console I/O to Terminal.
Product → Scheme → Edit Scheme → Options tab

About Swift 5.2 and new features of Simulator and Testing more on Medium:
https://medium.com/better-programming/whats-new-in-xcode-11-4-bd7c6f6bb0ba

Swift 5. What is new?

Dmytro Pylypenko — Mon, 28 Jan 2019 20:55:02 +0000

Swift 5 is ABI stable, which gives direct compatibility with OS without additional layers and backward compatibility between different versions of Swift, beginning from 5.0 version.

Also the new version has a lot of improvements:

Flattened try? with Optional type
No more double guard.
Raw strings
Gives one of the possibility to write a string without escaping characters inside. It's very feature for writing raw RegEx expressions in a clean way.

If you need to embed a variable inside a raw string, you must add hash symbol after backslash: #"(\\|\#(variable))"#
String interpolation
Declaration can be flexible and behave on your own.
For this, extend the protocol StringInterpolation with own function:
No recursion inside computed properties
Avoid additional layer for computations, and have it inside a closure.

It was a part of described features, more is there: https://developer.apple.com/documentation/xcode_release_notes/xcode_10_2_beta_release_notes/swift_5_release_notes_for_xcode_10_2_beta

Article on Medium: https://medium.com/@dimpiax/swift-5-what-is-new-examples-fbb64d525486

[Node.js] Using Local Module In Projects

Dmytro Pylypenko — Fri, 13 Oct 2017 18:41:59 +0000

Link to article at Medium: https://medium.com/@dimpiax/node-js-using-local-module-in-project-c6fb54bbc83a

You have several projects that use the same abstract libraries, you can hold “the same independent copy (not good) or create a private repository at npm.js.

I will share with you my experimental approach that is good in specific case.

File structure is next:

/serviceA
/serviceB
/library

Both services use same abstract classes / scripts from library, or a few of them. You can install local library as dependency simply putting local path to it.

Further examples will be with serviceA.

cd serviceA
npm i --no-save ../library

Important to not save dependency in package.json. Also npm creates alias to library, so after any changes you have a fresh version. After installing you can require your library’s dependency files as default.

Not bad, but what to do in production case?
For example, I have built a project using babel and want to add some additional files to built folder, that i will upload farther via git hook, scp or s3.

Use-case, in more details, uploading zip file to s3 and update Lambda function. There is no scenario to install dependencies inside lambda function, so need to put project as is.

Solution is to put your library by script inside build folder — not good, but works. Maybe sometime npm will support this approach by command.
Example: import syncManager from 'library/managers/syncManager'

Prepare package.json and some scripts inside.
package.json:

{
  "name": "serviceA",
  "version": "0.1.0",
  "main": "index.js",
  "config": {
    "sourceDir": "src",
    "buildDir": "dist",
    "library": {
      "name": "library",
      "path": "../library"
    }
  },
  "scripts": {
    "clean": "rimraf $npm_package_config_buildDir",
    "build:prod": "NODE_ENV=production npm run clean && mkdir $npm_package_config_buildDir && cp$npm_package_main package.json package-lock.json $npm_package_config_buildDir && cd $npm_package_config_buildDir && npm i",
    "pack:prod": "npm run build:prod && mkdir -p $npm_package_config_buildDir/node_modules/$npm_package_config_library_name && cp -r $npm_package_config_library_path/. $npm_package_config_buildDir/node_modules/$npm_package_config_library_name/.",
  },
  "author": "Dima Pilipenko <dimpiax@gmail.com>",
  "dependencies": {
  }
}

Pay attention that dependencies does not have an library mention.
By calling npm run pack:prod project is being prepared for farther use.

Hope this approach is useful for someone too :)

The end.

Dear reader, if you have some proposition or question about this approach — let’s discuss in comments.

Hi, I'm Pilipenko Dima

Dmytro Pylypenko — Tue, 10 Jan 2017 18:08:53 +0000

I have experience in IT over 10 years, and I am from beautiful city of Ukraine, in Kyiv.
Currently I live in Barcelona.

I use technologies for achieve and implement great products.
My knowledge are wide and deep.

More you can check and contact me on my personal website: https://dimpiax.com

Nice to meet this community.