#3634 [Core feature] raise warning when using default args in tasks that are not None Issue created by cosmicBboy ### Motivation: Why do you think this is important? Currently, flyte only supports default arguments in tasks that are

None

. We need to raise a warning if the user specifies any other value so that this feature isn't misused. ### Goal: What should the final outcome look like, ideally? When a user does something like: @task def t1( arg: Optional[str] = "", ) Flytekit should raise a warning, something like:

Only None can be used as a default argument in flyte tasks

### Describe alternatives you've considered NA ### Propose: Link/Inline OR Additional context No response ### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte