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

feat(import): [#129] Allow importing non-numeric M1 RisTags #133

Merged
merged 8 commits into from
Feb 26, 2023

Conversation

ursjoss
Copy link
Owner

@ursjoss ursjoss commented Feb 26, 2023

resolves #129.

  • Changes the data type of the property holding the M1 content in RisRecord from Long? to String?. This allows the import of ranges (e.g. "M1 - 1-2") or non-numeric chars (e.g. "M1 - 4es").
  • Deprecates RisRecord.number, in favor of new RisRecord.miscellaneous1
  • Deprecates RisRecord.typeOfWork, in favor of new RisRecord.miscellaneous3 - for consistency.
  • Fixes KRisTagTest and KRisTypeTest which were not asserted properly. Cleans up the Tag descriptions on the way.

@sonarcloud
Copy link

sonarcloud bot commented Feb 26, 2023

SonarCloud Quality Gate failed.    Quality Gate failed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell B 16 Code Smells

0.0% 0.0% Coverage
0.0% 0.0% Duplication

@ursjoss ursjoss changed the title feat(import): [#129] Change type of M1 from Long? to String? feat(import): [#129] Allow importing non-numeric M1 RisTags Feb 26, 2023
@ursjoss ursjoss marked this pull request as ready for review February 26, 2023 14:45
@ursjoss ursjoss merged commit fec6e6a into main Feb 26, 2023
@ursjoss ursjoss deleted the feat/129-M1_with_range branch February 26, 2023 14:56
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.

Parse Errors in Publisher RIS
1 participant