-
Notifications
You must be signed in to change notification settings - Fork 0
Support different fields for each key #18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support different fields for each key #18
Conversation
| const filterList = (typeof filter === "string" | ||
| ? [filter] | ||
| : filter | ||
| ).map((filter) => renderTemplate(filter, alibeezParams)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only filters are rendered now? Do you think it is enough? Also this is not obvious when writing the config. I'm not convinced about this change, especially since it seems to be out of scope with this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm pretty sure you told me we would never let the user choose for the fields they request because it can be abused, and I think it's a good thing.
| escape as escapeQuerystring, | ||
| } from "querystring"; | ||
| import { parse as parseQuerystring } from "querystring"; | ||
| import { parse as parseUrl } from "url"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't this the one that's deprecated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's in the the same module, see https://nodejs.org/api/url.html#url_url
|
Replaced by #19 |
No description provided.