Comments (3)
not sure if this is simple tbh. personally I consider the need to validate keys rare and due to badly designed APIs. also am more worried about issues like this: #2515 - because that is core to karate
the last line is honestly a bit hard to read and understand. so I'm concerned about that. you are welcome to try a PR
from karate.
Thanks @ptrthomas
Agreed about the last line being a bit hard to read.
For consistency with the other fuzzy markers, maybe declaring #dict as a property, not a key, would make more sense.
Something like:
{ data: #dict({
name: #string,
airports: #dict({
name: #string
}
}
Not sure it would be more understandable, though. And definitely very complicated to implement.
The other interesting thing in your comment is issue #2515. There's a risk, albeit small IMO, that this new marker would introduce a similar regression. Also, how would it integrate with contains [only [deep]]? Something to thing about ...
Anyway, I'm hoping to raise a PR for feedback in the coming days, with the initial suggestion.
from karate.
(on hold while looking at #2515 and learning more about shortcuts and whether they could help here. It seems that every month i learn a new amazing feature in Karate!)
from karate.
Related Issues (20)
- Schema validation Array issue HOT 2
- Test triggered from freestyle pipeline executes in Pool-Thread, where as test triggered from Multibranch pipeline executes from main HOT 1
- After first API response in a feature file, Cookie of next APIs are getting updated automatically to LAX category HOT 5
- Karate contains only shortcut fails in v1.4.1 HOT 4
- How to call Json Object as a Parameter in Karate feature HOT 1
- Schema validation doesn't support optional objects HOT 1
- Scenarios should be referenced by their name rather than line number
- Karate Robot cannot handle the ‘>’ character, yield org.graalvm.polyglot.PolyglotException: Invalid key code HOT 4
- karate.abort() response status == 500 HOT 3
- Karate robot cannot handle panes with "/" in name. Very niche problem HOT 1
- Variable reference lost after calling a scenario in separate feature HOT 3
- Not able to karate test case, getting issue HOT 1
- Karate summary reports not showing all tested features HOT 1
- [karate 1.4.1] OOM when load testing with mock for several minutes HOT 4
- Add Karate configuration option to disable the "no features or scenarios found" assertion HOT 1
- Does karate gating support Java DSL ? HOT 2
- Mutual SSL documented the wrong way HOT 3
- GraalVM changes incompatible with Karate HOT 10
- How to switch from Java selenium webdriver to Karate driver HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from karate.