Feature request: add custom properties to documents
See original GitHub issueBy supporting custom properties to be set for documents, you could specify e.g. the platform a program belongs to or the name of a team member that added a bunch of new domains.
This could look as follows:
bbrf new example --set platform:intigriti
bbrf domain add 'www.example.com' --set added_by:pieter 'comment:just stumbled across this'
This probably requires some checks on property names to ensure the integrity of the information, e.g. no reserved keywords like id
, _id
, _rev
or bbrf-related fields like domains
, ips
, url
, type
, etc. should be allowed.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:5 (4 by maintainers)
Top Results From Across the Web
4 ways to add custom properties to Word document - YouTube
Add custom properties in your document via built-in properties, sharepoint, fields and xml mapping.
Read more >[Feature Request] Pubsub Application / Custom Properties ...
Describe the feature. i.e. Azure Service Bus as a queueing system offers ability to set headers (next to the body) on the message....
Read more >Custom properties - CloudBees Documentation
You can create your own custom properties that can be used in Target groups or in the Configuration tab as criteria for feature...
Read more >Create and configure custom properties
Custom properties provide information for a specific document class. ... You can create custom properties in all types of AODocs library.
Read more >Node custom properties in dynamic query for applications
SolarWinds does listen to Feature Requests. Just middle-click on each of the below links to open them in a new tab and vote...
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 FreeTop 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
Top GitHub Comments
Great idea, this will make bbrf very extensible! Maybe it will be easier to prefix internally all custom fields (e.g
added_by
will becomex_added_by
which theoretically should fix the problem of name collisions.OK, I think found a way to reconcile all of the above by adding the subcommand
where
which accepts the following syntax:This works on
domains
,ips
andurls
and will query custom tags based on text-based comparisons as is defined in the Unicode Collation Algorithm as implemented by Couchdb.Since all values are stored as text, this allows date comparison if you store dates as unix timestamps or in a ISO-8601 format e.g.
2021-01-15T09:02:40.628Z
.That also means, however, that for example
"20"
comes after"1000"
, which makes this less suitable for integer comparison. So if you want to store integers, you may want to use padded zeros at the front to ensure that0020
comes before1000
.