Skip to content
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

Investigate sharing constants between JavaScript and Python #9

Open
fnesveda opened this issue Dec 6, 2022 · 2 comments
Open

Investigate sharing constants between JavaScript and Python #9

fnesveda opened this issue Dec 6, 2022 · 2 comments
Labels
t-tooling Issues with this label are in the ownership of the tooling team.

Comments

@fnesveda
Copy link
Member

fnesveda commented Dec 6, 2022

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.

@mtrunkat
Copy link
Member

mtrunkat commented Dec 8, 2022

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?

@jirimoravcik
Copy link
Member

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

@mtrunkat mtrunkat added the t-platform Issues with this label are in the ownership of the platform team. label Dec 16, 2022
@fnesveda 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t-tooling Issues with this label are in the ownership of the tooling team.
Projects
None yet
Development

No branches or pull requests

3 participants