91383269b9
This sounds a bit 'backwards' as the end goal here is to add an improved UX to partitions, not namespaces. The reason for doing it this way is that Namespaces already has a type of 'improved UX' CRUD in that it has one to many relationship in the form when saving your namespaces (the end goal for partitions). In moving Namespaces to use the same approach as partitions we: - Ensure the new approach works with one-to-many forms. - Test the new approach without writing a single test (we already have a bunch of tests for namespaces which are now testing the approach used by both namespaces and partitions) Additionally: - Fixes issue with missing default nspace in the nspace selector - In doing when checking to see that things where consistent between the two, I found a few little minor problems with the Admin Partition CRUD so fixed those up here also. - Removed the old style Nspace notifications |
||
|---|---|---|
| .. | ||
| application.js | ||
| auth-method.js | ||
| binding-rule.js | ||
| coordinate.js | ||
| dc.js | ||
| discovery-chain.js | ||
| http.js | ||
| intention.js | ||
| kv.js | ||
| node.js | ||
| nspace.js | ||
| oidc-provider.js | ||
| partition.js | ||
| permission.js | ||
| policy.js | ||
| proxy.js | ||
| role.js | ||
| service-instance.js | ||
| service.js | ||
| session.js | ||
| token.js | ||
| topology.js | ||