Skip to content

Conversation

@jpmckinney
Copy link
Contributor

@jpmckinney jpmckinney commented Jun 14, 2023

closes #88

Copy link

@m-aciek m-aciek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mind adding a test?

@jpmckinney
Copy link
Contributor Author

@m-aciek I've added a test and updated my commit with the suggestion.

Copy link

@m-aciek m-aciek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Thanks!

@rffontenelle
Copy link
Contributor

rffontenelle commented Jun 19, 2023

Confirmed it is working. It successfully adds "resource_name" field to each resource entry and pushing to Transifex sends the expected resource name. Thanks for that!

Can you also add a Feature entry to CHANGES file?

@jpmckinney
Copy link
Contributor Author

I've added an entry :)

@jpmckinney
Copy link
Contributor Author

Is there anything blocking a merge?

@AA-Turner
Copy link
Member

@jpmckinney tests failed on master, please could you provide a fix? Otherwise we'll need to revert.

A

@jpmckinney
Copy link
Contributor Author

I'll look into it!

@jpmckinney
Copy link
Contributor Author

I'm unable to reproduce and I installed the same versions of packages as listed by pip freeze in the workflow.

@jpmckinney
Copy link
Contributor Author

jpmckinney commented Oct 5, 2023

Aha, something changed in tx between 1.6.7 and 1.6.10. Looks like failures start with 1.6.8.

@jpmckinney
Copy link
Contributor Author

Okay, tx just changed the whitespace alignment: #96

@jpmckinney jpmckinney mentioned this pull request Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Transifex's tx client seems to have changed behavior for resource naming

4 participants