omarsotillo / nativeto Goto Github PK

• PR with cypress
• PRs with danger
• PRs with linters (prettier) -> public prettier file
• Connect to netlify plugins

In order to improve the distinction between the logical and view part let's move everything into different files

• Separate .ts from .html

Single input with target URL
Multiple options supporting the API from nativefier.

• Prepare Readme.md
• Protect branches
• License
• Development suggestions
• Create help needed issues for people interested.
• Create the initial tag.
• Define flow (PR, collaborators)

It will allow reducing people from dispatching request without really knowing what data are they sending. E.g: Could lead to the wrong use of the target platform

• Create netlify function handler
• Receive options req (DTO with defaults)
• Use nativefier
• Callback returns a zip file compressed
• Remove temporal app generated and compressed file after response.
• Optional: if Linux return a tar.gz file instea

Example of netlify functions:

exports.handler = async function(event) {
  // Query params
  // `?hi=5` -> { hi: 5 }
  console.log(event.queryStringParameters);
  // HTTP method (GET, POST, etc)
  console.log(event.httpMethod);
  // Request body (for non-GET requests)
  // In object form, no need to JSON.parse
  console.log(event.body);
  // Headers
  // Includes cookie, referer, origin, and all the typical
  // stuff you'd expect.
  console.log(event.headers)
}

Examples of nativefier API:

var nativefier = require('nativefier').default

// possible options, defaults unless specified otherwise
var options = {
  targetUrl: 'http://okubi.co',
}

nativefier(options, function (error, appPath) {
  if (error) {
    console.error(error)
    return
  }
  console.log('App has been nativefied to', appPath)
})

• Aggressive cypress
• Optional: unit tests
• Backend tests
• use cases tests -> 👀 https://github.com/mswjs/msw

Apply standard release protocol.

Define branches nomenclature in development file.

Add animations to the library as the modal. 🏖️ 🎴