Channels
datahub-flyte
scipy-2023-workshop
flyte-school
agent-support-memverge
flyte-build
flyte-users-berlin
scipy-2023-sprint
auth
flyte-bazel
large-language-models
contribute
bioinformatics-computational-biology
great-content
in-flyte-conversations
flyte-on-gcp
show-and-tell
shameless-promotion
linkedin-flyte
random
deployment
hacktoberfest-2023
flyte-github
feature-discussions
linen-test
flytelab
flytekit-java
integrations
ray-on-flyte
conference-talks
release
flyte-ui-ux
workflow-building-ui-proj
writing-w-sfloris
jobs
hacktoberfest-2022
torch-elastic
flyte-console
engineeringlabs
helsing-flyte
flyte-documentation
konan-integration
databricks-integration
ray-integration
wg-gpu-types
flytekit
ecosystem-unionml
scipy-2022-sprint
announcements
ask-the-community
flyte-deployment
introductions
events
Powered by
#ask-the-community
Title
# ask-the-community
y
Yi Chiu
08/10/2023, 7:02 AM
Hi community, I am working on
https://github.com/flyteorg/flyte/issues/3026
. What in my mind is adding a type transformer at
https://github.com/troychiu/flytekit/blob/edfa76739d1064822af44e0addc924e381d3a5ad/flytekit/core/type_engine.py#L1656
and adding a corresponding type at flyteidl. If this is correct, what's the flow of testing it? 1. Compile the proto and convert it as a python package. 2. Use the new generated package to test flytekit. Is it correct?
s
Samhita Alla
08/10/2023, 10:49 AM
cc
@Kevin Su
k
Kevin Su
08/10/2023, 5:06 PM
Hi. Welcome. you don’t really need to create a new type in IDL. you could just translate date to
Datetime
in idl • to_literal: python date ->
literal.duration
• to_python: literal.duration -> python date
Post