Microservice of conversion developed with Go:
- from nothing (only images) to PiFF
See the API documentation in API Blueprint format here
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
}
The title of a commit must follow this pattern : <type>(<scope>): <subject>
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
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