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

Update Vocalink data sets to v640 valid as of 12/10/2020 #23

Conversation

solanki-das
Copy link

No description provided.

Copy link
Contributor

@franciscocardoso franciscocardoso left a comment

Choose a reason for hiding this comment

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

Hi,

Can you please follow this example? In order to correctly update this module you need to do 3 things:

  1. Update the data file, which you have already done;
  2. Update the loadValacdos function;
  3. Update the docs folder with the correspondent version;

@solanki-das
Copy link
Author

solanki-das commented Nov 26, 2020 via email

@franciscocardoso
Copy link
Contributor

You are removing the pdf file. Please replace it with the new one instead.
Also, please don't forget to squash the commits into one. If you are not aware how to do it you can read this.

@solanki-das
Copy link
Author

solanki-das commented Nov 30, 2020 via email

@solanki-das
Copy link
Author

solanki-das commented Dec 8, 2020 via email

@franciscocardoso franciscocardoso force-pushed the Update-Vocalink-data-sets-to-v640-valid-as-of-12/10/2020 branch from 58bf630 to b7a768c Compare December 11, 2020 18:01
Copy link
Contributor

@franciscocardoso franciscocardoso left a comment

Choose a reason for hiding this comment

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

Hi @solanki-das
I took the liberty of squashing the commits.
Thanks for your contribution and effort to keep this module up to date.

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.

2 participants