not working

[leetomlee123]

Issue summary

Briefly describe the issue you are experiencing (or the feature you want to see added). Tell us what you were trying to do and what happened instead.

Remember, an issue is not the place to ask questions. You can use Stack Overflow for that.

Your environment

• Kong version = 1.1.1
• Kong Dashboard version = 3.6.0 (Kong Dashboard versions before 3.0.0 aren't supported anymore)
• Node version = #.#.#
• Npm version = #.#.#

Issue description

Current behavior

Tell us what happens.
any action not working, i`m use docker

Expected behavior

Tell us what should happen instead.

Steps to reproduce

Tell us how to reproduce this issue.

Good to have

Any screenshots? Browsers' logs?

[spiroo]

me too!

[CHOMNANP]

I'm having the same issue :D

[huangtao1]

I'm having the same issue...

[YixuanZeng]

I'm having the same issue...

[KylinHe]

I'm having the same issue... ovo~

[espider]

I'm having the same issue

[jlcoding]

I'm having the same issue

[akjamie]

having same issue

[yuleiqq]

having same issue

[davidback0420]

I'm having the same issue.

[TreeZhiyuan]

Does this project no longer maintained？

[towardsyoung]

Having same issue 1 years ago...

[ygm521]

Having same issue 1 years ago...

[guohailong2006]

哈哈哈哈，需要一个前端来fixed掉它

[m344739968]

why?

[yifengjin]

Having same issue

[hugbe8]

having same issue

[2030405043]

Having same issue

[kuoshijia]

Having same issue

[unil19]

there is some config missed for kong-schemas.js

you can either fill up your config for your version such as 1.1, 1.2, 1.3 or make the 1.0 config used by default when your kong version is above 1.0;
I solve the problems with the latter way by change the getter like this;
var Schema = { get: function(version) { var major = semver.major(version); var minor = major==0?semver.minor(version):0; return schemas[major + '.' + minor]; } };

[illyaMs]

@unil19 yeah, seems like a bad version check in schema helper (I must confess my hands are dirty here 😄).

Should be OK to use your second solution, since kong has a stable (1.x) version and (hopefully) those guys do respect semver.

Could you please create a MR, so the owner of the repo may merge it and publish? Seems like the issue is quite popular, so that'll be a great contribution.

[linuxdevopscn]

Having same issue

[illyaMs]

There's a fix done by @yaohx submitted in #220
Some tests did not pass, but I guess it won't be a big deal to fix them if needed.
We're using this forked version in our company currently: yaohx@369b5df

One more note is that the option provided above by @unil19 seems to be more elegant, imho (so maybe this could also be sent as a PR).

Whatever option is preffered, I think we need @PGBI to intervene as he's the maintainer (and thus the only person that can merge these fixes to upstream and release/tag an updated docker image).