Skip to content

A microservice converting various input formats to PiFF format for the Taliesin app

Notifications You must be signed in to change notification settings

taliesin-insa/micro-conversion

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

76 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Conversion

Microservice of conversion developed with Go:

  • from nothing (only images) to PiFF

Exposed REST API

See the API documentation in API Blueprint format here

PiFF structures

Here is the decomposition of the piFF structure used in this microservice:

type Meta struct {
	Type string
	URL  string
}
type Location struct {
	Type    string
	Polygon [][2]int
	Id      string
}
type Data struct {
	Type       string
	LocationId string
	Value      string
	Id         string
}
type PiFFStruct struct {
	Meta     Meta
	Location []Location
	Data     []Data
	Children []int
	Parent   int
}

Commits

The title of a commit must follow this pattern : <type>(<scope>): <subject>

Type

Commits must specify their type among the following:

  • build: changes that affect the build system or external dependencies
  • debug: a code change to debug (logs, etc.)
  • docs: documentation only changes
  • feat: a new feature
  • fix: a bug fix
  • perf: a code change that improves performance
  • refactor: modifications of code without adding features nor bugs (rename, white-space, etc.)
  • style: CSS, layout modifications or console prints
  • test: tests or corrections of existing tests
  • ci: changes to our CI configuration

Scope

Your commits name should also precise which part of the project they concern. You can do so by naming them using the following scopes:

  • General
  • Conversion
  • API
  • Configuration

About

A microservice converting various input formats to PiFF format for the Taliesin app

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •