gojek/optimus-extension-valor

GO-JEK Technologies

Description

Middleman-Powered GO-JEK Technologies's Website 👻 🕸 hosted with ❤️ by GitHub

GO-JEK Technologies generates matter for GO-JEK Technologies on GitHub Pages

Building

try, 
  make clean
  make setup
  make install
  make serve

or just,
  make

License

Copyright 2018, GO-JEK Technologies <http://www.gojek.io>

optimus-extension-valor's Issues

Not Found Resource/Framework

• Bug

This case could be found when the user uses the result of the previous pipeline as the input in the current pipeline. This is because the current Valor loads all the resources/framework in its life cycle. The problem is if the output is not written yet, but it's being loaded.

• Solution

One possible solution is by loading on demand. Meaning, loading is done only when the resource/framework is required. So, no loading all data first.

Documentation

More comprehensive documentation is essential for adoption. List of topics to be covered:

• quick start for validate only
• quick start for evaluate only
• quick start for both validate and evaluate
• reference for recipe pipeline frlow
• reference for building recipe and its example
• reference for building JSON Schema and its example
• reference for building JSONnet and its example

Refactor

Refactor is required to make the code cleaner and easier to read. List of some parts that need to be refactored:

• making progress bar into a plugin
• restructure data loader for Resource and Framework
• restructure model package
• reorganize naming, such as the use of recipe for Framework
• adding unit Test
• allows recipes to be read from a specified path, prioritized
• restructure how a snippet looks like
• instead of only appending one procedure with the other, it's more make sense to make it as a kind of pipeline
• performance improvement