Catalog package number configuration does not accept floating point
nLight opened this issue · 11 comments
May I take this issue?
@Viscontes please go ahead 🙇
@nLight I am sorry but I cannot install project locally. How could I get some help?
@Viscontes sure, no worries! What stage you are at?
@nLight I installed mesos project and dcos-ui project. However, in dcos-ui/src/webui I did not have master folder. I tried to launch server in webui folder but on localhost:8000/mesos I got 404: File not found. I don't know what to do. Maybe you have some ideas how to fix this?
Hi @Viscontes! You should not need anything except the UI. If you follow the install instructions https://github.com/dcos/dcos-ui#local-development and replace src/js/config/Config.dev.ts with:
// Configuration overrides
export default {
analyticsKey: "39uhSEOoRHMw6cMR6st9tYXDbAL3JSaP",
rootUrl: "",
historyServer: "",
// Override cluster's uiConfiguration for development
uiConfigurationFixture: {
uiConfiguration: {
plugins: {
banner: {
enabled: false
},
intercom: {
enabled: false,
appId: "wn4z9z0y"
},
mesos: {
"logging-strategy": "logrotate"
},
oauth: {
enabled: false,
authHost: "https://dcos.auth0.com"
},
"overview-detail": {
enabled: true
},
tracking: {
enabled: false
}
}
},
clusterConfiguration: {
firstUser: true,
id: "ui-fixture-cluster-id"
}
},
// Use fixtures to mock API requests
useFixtures: true,
// Use uiConfigurationFixture defined above
useUIConfigFixtures: true
};after npm start the UI should be available at http://localhost:4200
@nLight Thank you a lot. Is it okay that I have 504 errors and Uncaught TypeError: Cannot read property 'success' of null ?
@Viscontes our fixtures aren't 100% solid, does it block you from getting to the form?
I tried illustrating the bug:
With fixtures it's not going to be Cassandra, but the important point is to fix decimal fields.
Thanks!
@nLight for me it looks like this.
I have this picture on every package. I just cannot open that form. Could you please suggest me something?
Hi @Viscontes, just hit Review and run to get to the form. It will look different, because it's a different package, but then the bug should be reproducible on any <input type="number" /> field.