Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / odata2ts/odata2ts issues and pull requests
#184 - fix(odata2ts): duplicate output paths
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#184 - fix(odata2ts): duplicate output paths
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#184 - fix(odata2ts): duplicate output paths
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#184 - fix(odata2ts): duplicate output paths
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#184 - fix(odata2ts): duplicate output paths
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#184 - fix(odata2ts): duplicate output paths
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#184 - fix(odata2ts): duplicate output paths
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#184 - fix(odata2ts): duplicate output paths
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#183 - feat(odata2ts): support TypeDefinition elements
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#183 - feat(odata2ts): support TypeDefinition elements
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#183 - feat(odata2ts): support TypeDefinition elements
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#183 - feat(odata2ts): support TypeDefinition elements
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#183 - feat(odata2ts): support TypeDefinition elements
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#182 - fix(odata2ts): use qualified name for bound operations
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#182 - fix(odata2ts): use qualified name for bound operations
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#182 - fix(odata2ts): use qualified name for bound operations
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#181 - feat(odata2ts): support schema alias
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#181 - feat(odata2ts): support schema alias
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#180 - chore(deps): bump yaml from 2.2.1 to 2.3.1
Pull Request -
State: closed - Opened by dependabot[bot] over 1 year ago
Labels: dependencies
#180 - chore(deps): bump yaml from 2.2.1 to 2.3.1
Pull Request -
State: closed - Opened by dependabot[bot] over 1 year ago
Labels: dependencies
#180 - chore(deps): bump yaml from 2.2.1 to 2.3.1
Pull Request -
State: closed - Opened by dependabot[bot] over 1 year ago
Labels: dependencies
#180 - chore(deps): bump yaml from 2.2.1 to 2.3.1
Pull Request -
State: closed - Opened by dependabot[bot] over 1 year ago
Labels: dependencies
#179 - generated d.ts file located at wrong path
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#179 - generated d.ts file located at wrong path
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#179 - generated d.ts file located at wrong path
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#179 - generated d.ts file located at wrong path
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#179 - generated d.ts file located at wrong path
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#179 - generated d.ts file located at wrong path
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#179 - generated d.ts file located at wrong path
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#179 - generated d.ts file located at wrong path
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#179 - generated d.ts file located at wrong path
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#178 - OData Actions: Multiple exports with identical name generated
Issue -
State: closed - Opened by heimwege over 1 year ago
- 3 comments
#178 - OData Actions: Multiple exports with identical name generated
Issue -
State: closed - Opened by heimwege over 1 year ago
- 3 comments
#178 - OData Actions: Multiple exports with identical name generated
Issue -
State: closed - Opened by heimwege over 1 year ago
- 3 comments
#178 - OData Actions: Multiple exports with identical name generated
Issue -
State: closed - Opened by heimwege over 1 year ago
- 3 comments
#178 - OData Actions: Multiple exports with identical name generated
Issue -
State: closed - Opened by heimwege over 1 year ago
- 3 comments
#178 - OData Actions: Multiple exports with identical name generated
Issue -
State: closed - Opened by heimwege over 1 year ago
- 3 comments
#178 - OData Actions: Multiple exports with identical name generated
Issue -
State: closed - Opened by heimwege over 1 year ago
- 3 comments
#177 - Parsing metadata with ComplexType using TypeDefinition is not possible
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#177 - Parsing metadata with ComplexType using TypeDefinition is not possible
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#177 - Parsing metadata with ComplexType using TypeDefinition is not possible
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#177 - Parsing metadata with ComplexType using TypeDefinition is not possible
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#177 - Parsing metadata with ComplexType using TypeDefinition is not possible
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#177 - Parsing metadata with ComplexType using TypeDefinition is not possible
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#177 - Parsing metadata with ComplexType using TypeDefinition is not possible
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
#176 - Parsing metadata with Singleton entity is not possible
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
Labels: bug
#176 - Parsing metadata with Singleton entity is not possible
Issue -
State: closed - Opened by heimwege over 1 year ago
- 3 comments
#176 - Parsing metadata with Singleton entity is not possible
Issue -
State: closed - Opened by heimwege over 1 year ago
- 4 comments
#176 - Parsing metadata with Singleton entity is not possible
Issue -
State: closed - Opened by heimwege over 1 year ago
- 3 comments
#176 - Parsing metadata with Singleton entity is not possible
Issue -
State: open - Opened by heimwege over 1 year ago
- 5 comments
#176 - Parsing metadata with Singleton entity is not possible
Issue -
State: open - Opened by heimwege over 1 year ago
- 5 comments
Labels: bug
#176 - Parsing metadata with Singleton entity is not possible
Issue -
State: open - Opened by heimwege over 1 year ago
- 5 comments
Labels: bug
#176 - Parsing metadata with Singleton entity is not possible
Issue -
State: closed - Opened by heimwege over 1 year ago
- 6 comments
Labels: bug
#175 - feat(odata2ts): better namespace support
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#175 - feat(odata2ts): better namespace support
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#174 - Parsing metadata with multiple namespaces is not possible
Issue -
State: closed - Opened by lpmusicon over 1 year ago
- 5 comments
#174 - Parsing metadata with multiple namespaces is not possible
Issue -
State: closed - Opened by lpmusicon over 1 year ago
- 5 comments
#174 - Parsing metadata with multiple namespaces is not possible
Issue -
State: closed - Opened by lpmusicon over 1 year ago
- 5 comments
#174 - Parsing metadata with multiple namespaces is not possible
Issue -
State: closed - Opened by lpmusicon over 1 year ago
- 5 comments
#174 - Parsing metadata with multiple namespaces is not possible
Issue -
State: closed - Opened by lpmusicon over 1 year ago
- 5 comments
#174 - Parsing metadata with multiple namespaces is not possible
Issue -
State: closed - Opened by lpmusicon over 1 year ago
- 5 comments
#173 - feat(odata2ts): generate comments for model properties
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#173 - feat(odata2ts): generate comments for model properties
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#173 - feat(odata2ts): generate comments for model properties
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#173 - feat(odata2ts): generate comments for model properties
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#172 - chore: update dependencies
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#172 - chore: update dependencies
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#172 - chore: update dependencies
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#172 - chore: update dependencies
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#171 - refactor(http-client-api): move to http-client repo
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#171 - refactor(http-client-api): move to http-client repo
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#170 - refactor: remove deprecated packages
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#170 - refactor: remove deprecated packages
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#169 - fix(examples): use newest versions & http-client packages
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#169 - fix(examples): use newest versions & http-client packages
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#169 - fix(examples): use newest versions & http-client packages
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#169 - fix(examples): use newest versions & http-client packages
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#169 - fix(examples): use newest versions & http-client packages
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#169 - fix(examples): use newest versions & http-client packages
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#169 - fix(examples): use newest versions & http-client packages
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#168 - fix(odata-query-objects): wrong imports
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#168 - fix(odata-query-objects): wrong imports
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#168 - fix(odata-query-objects): wrong imports
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#168 - fix(odata-query-objects): wrong imports
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#168 - fix(odata-query-objects): wrong imports
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#168 - fix(odata-query-objects): wrong imports
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#168 - fix(odata-query-objects): wrong imports
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#167 - refactor: remove deprecated packages
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#167 - refactor: remove deprecated packages
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#167 - refactor: remove deprecated packages
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#167 - refactor: remove deprecated packages
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#166 - refactor: replace odata-client-api with http-client-api
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#166 - refactor: replace odata-client-api with http-client-api
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#166 - refactor: replace odata-client-api with http-client-api
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#166 - refactor: replace odata-client-api with http-client-api
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#166 - refactor: replace odata-client-api with http-client-api
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#166 - refactor: replace odata-client-api with http-client-api
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#166 - refactor: replace odata-client-api with http-client-api
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#166 - refactor: replace odata-client-api with http-client-api
Pull Request -
State: closed - Opened by texttechne over 1 year ago
#165 - feat(fetch-client): fetch odata client
Pull Request -
State: closed - Opened by texttechne over 1 year ago