You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, we have some constants duplicated between the @apify/consts NPM package and the Python Client and Python SDK. We should look into how to have them defined only in one place and shared between all the projects.
The text was updated successfully, but these errors were encountered:
Yeah. Can we add some action to apify-shared that every time apify/consts is published it takes it, transforms to some Python compatible format and publishes it as pip package?
Yeah. Can we add some action to apify-shared that every time apify/consts is published it takes it, transforms to some Python compatible format and publishes it as pip package?
Another possibility is some json or yaml file as the source of truth and we create language-specific constants from that
fnesveda
added
t-tooling
Issues with this label are in the ownership of the tooling team.
and removed
t-platform
Issues with this label are in the ownership of the platform team.
labels
Nov 5, 2024
Right now, we have some constants duplicated between the
@apify/consts
NPM package and the Python Client and Python SDK. We should look into how to have them defined only in one place and shared between all the projects.The text was updated successfully, but these errors were encountered: