Skip to content

Create developer_tutorial.md#1

Draft
jornh wants to merge 1 commit intomasterfrom
jornh-developer-tutorial
Draft

Create developer_tutorial.md#1
jornh wants to merge 1 commit intomasterfrom
jornh-developer-tutorial

Conversation

@jornh
Copy link
Copy Markdown
Owner

@jornh jornh commented Oct 3, 2019

Summary of Changes

  • by example/tours
  • model -> extractor

    • simple core Neo4j
    • add stuff to it - with stuff being: X
      Extractor - base SQL 1:1 -/
      Another —- schema/Frictionless Data ... Ingest from RestAPI/Swagger etc - non-swagger...? Grab stuff in Airflow db...
  • (real extractors - flavors

Include a summary of changes then remove this line

Tests

What tests did you add or modify and why? If no tests were added or modified, explain why. Remove this line

Documentation

What documentation did you add or modify and why? Add any relevant links then remove this line

CheckList

Make sure you have checked all steps below to ensure a timely review.

  • PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"
  • PR includes a summary of changes.
  • PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
  • In case of new functionality, my PR adds documentation that describes how to use it.
    • All the public functions and the classes in the PR contain docstrings that explain what it does
  • PR passes make test
  • I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant