how to deprecate types? #91
Labels
No labels
bugfix
cleanup
discussion
documentation
doing
done
feature
improvement
packaging
Stale
testing
TODO
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: ungleich-public/cdist#91
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
since
__file
has--onchange
now, then__config_file
is redundant.same with
__apt_key_uri
, if I add--uri
to__apt_key
(!779).maybe symlink
__config_file
to__file
and__apt_key_uri
to__apt_key
, because parameters are compatible?i, myself, would just remove them and write that in changelog IN CAPS. dragging along legacy is tiresome.
closed
Resolved in https://code.ungleich.ch/ungleich-public/cdist/merge_requests/783
mentioned in merge request !783
assigned to @poljakowski
@steven Do you perhaps have a better idea?
@nico But, with default saving output streams, type stderr output won't be explicitly visible.
Yes, that is even better, output WARN in type code and then remove it, no need for core changes. I like it :)
Easy solution in general: output warning to STDERR. Remove in the next or overnext major version.
Regarding some type parameter, type's implementation is responsible for deprecation warning on deprecated parameter usage.
@ander @nico How about adding
deprecated
type marker? On such type usage cdist logs warning line. And after some time we remove the type.changed the description