Feature: Expose --id to rules
See original GitHub issueI want to get the value of danger ci --id
to use in rules.
The intent is to run danger twice on CI pipeline, first time early to report coding errors, second time late to grab any artifacts from CI jobs and format them as comments.
The property itself is here:
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Exposing Database IDs to the UI - Stack Overflow
Rules on 'who can access what ids' must be very very carefully built into your application when exposing these ids.
Read more >Keep IDs internal with REST by Mark Seemann - ploeh blog
I wanted to see if it would be possible to design a REST API that doesn't expose IDs in their JSON (or XML)...
Read more >A Better Way to Protect Your IDs - Medium
Your web application has a strong way of authentication and every resource has checks if your user is actual authorized to access it....
Read more >Feature Toggles (aka Feature Flags) - Martin Fowler
Expose current feature toggle configuration Any system using feature flags should expose some way for an operator to discover the current state of...
Read more >Access-Control-Expose-Headers - HTTP - MDN Web Docs
The Access-Control-Expose-Headers response header allows a server to indicate which response headers should be made available to scripts ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think
dangerID
in there would be 👍🏻 (utils is for functions IMO)Feels like a field which could be available in the main danger export to me