mirror of
https://github.com/mageddo/dns-proxy-server.git
synced 2026-04-25 01:15:52 +03:00
[PR #122] [MERGED] Refactoring Storage API #286
Labels
No labels
bug
confirmed
discussion
duplicate
enhancement
feature
feature-request
not-planned
pull-request
secondary-feature
stale
triage
waiting-feedback
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/dns-proxy-server-mageddo#286
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/mageddo/dns-proxy-server/pull/122
Author: @mageddo
Created: 4/21/2019
Status: ✅ Merged
Merged: 4/22/2019
Merged by: @mageddo
Base:
master← Head:feature/121📝 Commits (10+)
c058435extracting storage vos from config package01fbc4afixing cyclic referencea6f5e43refactoring packageab72ed1renaming structs4a98e90reordering methods and removing commentsc10f742implementing maps, id is not necessary anymore0ea0c66fixing config mappinga859f6erefactoring package7039712fixing env apiea23e46fixing envs retrieve📊 Changes
33 files changed (+1086 additions, -486 deletions)
View changed files
📝
.travis.yml(+5 -2)📝
Dockerfile.builder(+3 -0)➕
Dockerfile.go.builder(+6 -0)📝
RELEASE-NOTES.md(+4 -0)📝
VERSION(+1 -1)📝
builder.bash(+4 -0)📝
conf/conf.go(+4 -3)📝
conf/conf_test.go(+6 -3)📝
controller/v1/cache.go(+1 -1)📝
controller/v1/cache_test.go(+1 -1)📝
controller/v1/env.go(+35 -39)📝
controller/v1/env_test.go(+41 -18)📝
controller/v1/hostname.go(+27 -33)📝
controller/v1/hostname_test.go(+54 -20)📝
controller/v1/index.go(+4 -3)📝
controller/v1/statics.go(+1 -1)➕
controller/v1/vo/env.go(+30 -0)➕
controller/v1/vo/hostname.go(+61 -0)📝
dns.go(+8 -4)📝
docker-compose.yml(+25 -6)...and 13 more files
📄 Description
Refactoring storage API separating the vos that are used to store, respond the rest api and used at the DNS questions, this will be helpful when a new store api version required
Tasks
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.