kyy/swagger-ui
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: deeplinked operation resolution (#4281)

Browse Source 
* Use `parameterWithMeta` to get parameter data in <ParameterRow>

* Prefer specPath when fetching resolved subtrees in OperationContainer

* Add test for OAS3 callback rendering

* Remove debugger statement

* Pass base resolution URL directly to Swagger-Client subtree resolver

* Remove accidental comment

* Migrate additional options

* Don't default to empty Map when getting subtree
This commit is contained in:
kyle
2018-03-02 16:26:37 -08:00
committed by GitHub
parent 4fd7f1d099
commit feef20dd67
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/core/containers/OperationContainer.jsx
View File

@@ -126,10 +126,10 @@ export default class OperationContainer extends PureComponent {
} = this.props
if(specPath) {
return specSelectors.specResolvedSubtree(specPath.toJS()) || Map()
return specSelectors.specResolvedSubtree(specPath.toJS())
}
return specSelectors.specResolvedSubtree(["paths", path, method]) || Map()
return specSelectors.specResolvedSubtree(["paths", path, method])
}
requestResolvedSubtree = () => {
@@ -182,10 +182,10 @@ export default class OperationContainer extends PureComponent {
const Operation = getComponent( "operation" )
const resolvedSubtree = this.getResolvedSubtree()
const resolvedSubtree = this.getResolvedSubtree() || Map()
const operationProps = fromJS({
op: resolvedSubtree || Map(),
op: resolvedSubtree,
tag,
path,
summary: unresolvedOp.getIn(["operation", "summary"]) || "",