Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / acolono/opencounter_core issues and pull requests

#29 - throw appropriate exceptions

Issue - State: open - Opened by rosenstrauch over 7 years ago

#28 - Create initial Release using gulp task

Issue - State: closed - Opened by rosenstrauch about 8 years ago

#27 - Scenario: Create Single New Counter

Issue - State: closed - Opened by rosenstrauch about 8 years ago
Labels: descriptions

#26 - Getting the value for a single counter

Issue - State: closed - Opened by rosenstrauch about 8 years ago
Labels: descriptions

#25 - Scenario: reset a Single Counter

Issue - State: closed - Opened by rosenstrauch about 8 years ago
Labels: descriptions

#24 - Scenario: prevent deleting nonaccessible (authscope, counter status)

Issue - State: open - Opened by rosenstrauch about 8 years ago
Labels: descriptions

#23 - Scenario: delete multiple counters

Issue - State: open - Opened by rosenstrauch about 8 years ago
Labels: descriptions

#22 - Scenario: attempt to delete nonexisting counter

Issue - State: open - Opened by rosenstrauch about 8 years ago
Labels: descriptions

#21 - trigger build of slimcounter canary branch

Issue - State: open - Opened by rosenstrauch over 8 years ago
Labels: CI

#20 - Run codestyle checks and linters

Issue - State: closed - Opened by rosenstrauch over 8 years ago - 1 comment
Labels: CI

#19 - Build documentation and push it to public environment

Issue - State: closed - Opened by rosenstrauch over 8 years ago
Labels: CI

#18 - CI: Semantic Versioning DEADLINE:

Issue - State: closed - Opened by rosenstrauch over 8 years ago
Labels: CI

#17 - CI: pick changelog generator

Issue - State: open - Opened by rosenstrauch over 8 years ago
Labels: CI

#16 - Scenario: Delete Existing Counters via name or ID

Issue - State: closed - Opened by rosenstrauch over 8 years ago
Labels: descriptions

#15 - Scenario: Index/List/Get Muliple Counters

Issue - State: closed - Opened by rosenstrauch over 8 years ago - 2 comments
Labels: descriptions

#14 - Scenario: get default counter

Issue - State: open - Opened by rosenstrauch over 8 years ago
Labels: descriptions

#13 - Scenario: get a single non-existing counter

Issue - State: open - Opened by rosenstrauch over 8 years ago
Labels: descriptions

#12 - Scenario: get a single existing counter representation

Issue - State: closed - Opened by rosenstrauch over 8 years ago
Labels: duplicate, descriptions

#11 - Create and update multiple new counters

Issue - State: open - Opened by rosenstrauch over 8 years ago
Labels: descriptions

#10 - Scenario: creating default counter

Issue - State: open - Opened by rosenstrauch over 8 years ago
Labels: descriptions

#9 - Scenario: creating new counter with invalid name

Issue - State: open - Opened by rosenstrauch over 8 years ago
Labels: descriptions

#8 - Scenario: creating new counter if name already taken

Issue - State: open - Opened by rosenstrauch over 8 years ago
Labels: descriptions

#7 - Scenario: Geting a non-existing Counter field

Issue - State: open - Opened by rosenstrauch over 8 years ago
Labels: descriptions

#6 - Scenario: Getting the status for a single counter in the collection

Issue - State: open - Opened by rosenstrauch over 8 years ago
Labels: descriptions

#5 - Scenario: Getting a representation of a counter

Issue - State: closed - Opened by rosenstrauch over 8 years ago
Labels: descriptions

#4 - When detecting a merge request from a feature branch for opencounter

Issue - State: open - Opened by rosenstrauch over 8 years ago
Labels: CI

#3 - Logging in counter controller

Issue - State: open - Opened by rosenstrauch over 8 years ago
Labels: enhancement

#2 - GET /counters/{name}/value does not reply with json

Issue - State: closed - Opened by piccaso over 8 years ago - 2 comments
Labels: bug

#1 - Missing db lock Multiple Concurrent Counter Increments Using SqlCounterRepository

Issue - State: open - Opened by Nebel54 over 8 years ago - 3 comments
Labels: bug