DEV Community: Daniel Newell

Drafts

Daniel Newell — Wed, 09 Dec 2020 17:40:53 +0000

WHERE DID ALL MY DRAFTS GO!?!?!

Please help. I'm in mild distress now.

ForemJS Test Article

Daniel Newell — Fri, 18 Sep 2020 13:08:00 +0000

Test

This is an article written using the ForemJS API Wrapper. GitHub

Introducing ForemJS: The API Wrapper for Dev.to

Daniel Newell — Fri, 18 Sep 2020 02:20:08 +0000

If you hadn't already known, Dev.to has access to an API. You can access it here. For my lovely NodeJS developers, I've started developing an open-souce API wrapper for it called ForemJS.

foremjs / foremjs

A NodeJS wrapper for https://docs.forem.com/api/

Currently, it is very limited but I have plans to cover the entire API. ForemJS runs asynchronously, so you will have to use await, or .then() callbacks. I am currently working on documentation, but here are the basics of how it works.

Step 1 - Install the Package

npm i foremjs@0.1.x

As by SemVer, while the MAJOR version is still 0, breaking changes may occur. The PATCH versions (0.1.x) are going to be adding documentation, and polished up the wrapper as per people's specifications. The next MINOR (0.2.0) version should cover more of the API and get ready for 1.0.0.

Step 2 - Require the Package

const Forem = require('foremjs')

This is a simple process of just requiring the package.

Step 3 - Create a Client

You will have to get a token from your settings page. Now use the following code to create an instance. This is how you will access the API.

const client = new Forem.Client(TOKEN)

Step 4 - Use the API

You can use .getArticle(id) to get an article. These are some of the properties carried by the Article class: .title, .description, and .url. You can see the code for the whole list. There is also .getUser(id), however, it is a bit limited by the API itself. You can get things like .createdAt, and .github for their username.

More features are soon to come, such as posting articles. Thank you so much for reading this article. Maybe my next one will be posted using my wrapper? Seriously, though, if you have any questions, comments, or concerns about this project comment them down below and I will respond as soon as possible.

I'm Daniel Newell, and I support women devs.

Daniel Newell — Thu, 17 Sep 2020 13:16:35 +0000

What is equality?

Equality is not a complicated issue. It is definitely not up for debate. We all have to support devs regardless of age, gender, sexual orientation, disability, race, etc. We all share the same love for creating websites, applications, and more. Equality is the equal treatment of all people regardless of characteristics.

How I ensure equality (and how you should too)

I ensure that I work with people regardless of any characteristic. Sme of the best developers I knore are female or non-binary. Being part of it, I also work with the LGBTQ+ community. This isn't something you should brag about, it's human decency.

To my female and enby developer friends:

You rock! You are wonderful beings who shouldn't be belittled because of your gender identity. You can do anything anybody else can do, I know it. Keep coding. :)

Localise your NodeJS app easily with i18n

Daniel Newell — Tue, 15 Sep 2020 15:25:23 +0000

So, you have a NodeJS app, but you only have access to a small subset of people: those who speak your language. Or maybe you have translations, but they are inefficient to implement and take up valuable time you can be using for fixing issues or adding features. In this article, you will learn how to implement Localazy to your NodeJS project.

Localazy is a translation management platform and it's a great option for developers because of two key features:

It comes with ShareTM allowing you to automatically translate your app into 80+ languages for free by sharing translations with other developers.
With its CLI, it can be easily integrated into any workflow. And we are using the CLI today.

By the way, this tool is free. Pretty cool, right?

Part 1 - Getting Ready

Create a Localazy account and follow prompts. Create an app, add your languages, and add translators.

Now, install.

Create a file called localazy.json and paste the following. Make sure to gather your keys!

{

  "writeKey": "your-apps-write-key", 
  "readKey": "your-apps-read-key",

  "upload": {
    "type": "json",
    "files": "locales/en.json"
  },

  "download": {
    "files": "locales/${lang}.json"
  }

Now, we can upload translations. Create en.json and edit as needed.

{
"appName": "Your Cool App",
"error": "An error has occurred.",
"Hello": "Hello {{name}}"
}

Now run localazy upload and you should see your translation strings on your home screen. You can use automatic or manual translations. Automatic translations may not be the most accurate, but are a start. When complete, use localazy download to gather edited files.

Part 2 - Development

Install i18n via npm. In your code add the following.

const i18n = require('i18n')
i18n.configure({
  locales: ['en', 'es', 'de'] // your languages
  directory: path.join(__dirname, '/locales'),
  register: global
})
function translate (p, l, ph) {
  return __({ phrase: p, locale: l}, ph)
}

Now, to translate anything, use the translate() function, like so:

console.log(translate('hello', 'de', { name: 'Daniel' }))

Implement this to fit your code, and you are complete!

If you run into issues, please leave a message and I will fix it as soon as possible.

Edited on 15 September: Basic style changes and fixed an oversight