-
-
Notifications
You must be signed in to change notification settings - Fork 335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added deprecated to enums #2342
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
<div *ngIf="item?.isDeprecated" class="doc-viewer-item-query-deprecated"> | ||
<span class="doc-viewer-item-query-deprecated-title"> | ||
{{ 'DOCS_DEPRECATED_TEXT' | translate }} | ||
</span> | ||
<span markdown [data]="item?.deprecationReason ?? ''"> </span> | ||
</div> |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
import { ComponentFixture, TestBed } from '@angular/core/testing'; | ||
|
||
import { DocViewerDeprecatedComponent } from './doc-viewer-deprecated.component'; | ||
|
||
describe('DocViewerDeprecatedComponent', () => { | ||
let component: DocViewerDeprecatedComponent; | ||
let fixture: ComponentFixture<DocViewerDeprecatedComponent>; | ||
|
||
beforeEach(async () => { | ||
await TestBed.configureTestingModule({ | ||
declarations: [ DocViewerDeprecatedComponent ] | ||
}) | ||
.compileComponents(); | ||
|
||
fixture = TestBed.createComponent(DocViewerDeprecatedComponent); | ||
component = fixture.componentInstance; | ||
fixture.detectChanges(); | ||
}); | ||
|
||
it('should create', () => { | ||
expect(component).toBeTruthy(); | ||
}); | ||
}); |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
import { Component, Input } from '@angular/core'; | ||
import { GraphQLEnumValue, GraphQLField } from 'graphql'; | ||
|
||
@Component({ | ||
selector: 'app-doc-viewer-deprecated', | ||
templateUrl: './doc-viewer-deprecated.component.html', | ||
styles: [], | ||
}) | ||
export class DocViewerDeprecatedComponent { | ||
@Input() item?: GraphQLField<any, any> | GraphQLEnumValue; | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -15,15 +15,15 @@ | |
"@types/supertest": "^2.0.11", | ||
"jest": "29.4.1", | ||
"koa": "^2.13.1", | ||
"koa-send": "^5.0.1", | ||
"nodemon": "^2.0.12", | ||
"supertest": "^6.1.6", | ||
"ts-jest": "29.0.5", | ||
"ts-node": "^10.2.1", | ||
"typescript": "4.9.5" | ||
}, | ||
"peerDependencies": { | ||
"@koa/router": "~11.0.2", | ||
"koa-send": "^5.0.1" | ||
Comment on lines
-25
to
-26
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. These were semver major changes, but they were published in non semver major version changes. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sorry I'm not sure I follow. You mean I should have published a major version since the change is major? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Yes. Anytime a package makes its peer dependency requirements tighter (require newer versions), it's a breaking change that should be published in a semver major version increment. Packages that were previously using There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Got it. I can publish a major version next but I don't think that would fix the issue with those packages, as they would need to update manually. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm a bit rusty about the correct way to fix an accidentally major change in a minor/patch release, but maybe what you could do is revert the major changes in an other patch release so that way people using There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sounds good |
||
"@koa/router": "^12.0.1" | ||
}, | ||
"engines": { | ||
"node": ">= 12" | ||
|
@@ -32,7 +32,6 @@ | |
"type": "opencollective", | ||
"url": "https://opencollective.com/altair" | ||
}, | ||
"gitHead": "e5ce60f5a14997f1471a961ac76efacbb044df46", | ||
"homepage": "https://github.com/altair-graphql/altair#readme", | ||
"keywords": [ | ||
"altair", | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was it added to dev dependencies, instead of dependencies? It's used in the published code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah that was by mistake. Thanks for spotting it.