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

enhancement-TMCR-add ACCEPTED DRIVER PERMITs #408

Closed

Conversation

nick-knowles
Copy link
Contributor

Add ACCEPTED DRIVER PERMITS to SIMPLE VEHICLE TYpe

seime and others added 14 commits April 29, 2022 09:04
* Removed comment about which editor made the change

* Removed comment about which editor was used
* Added Spotless tool to verify and correct xsd/xml file formatting

* Attempt at making Travis validate

* Add more JVM memory, appears to speed up the formatting process

* Only require reformatting of files that have changed since 'master' branch

* Improved documentation

* More docs on formatting

* Fix command line option

* Replaced shall with must for character encoding

* Initial reformatting using Spotless - rules from Eclipse WTP project located in eclipsecodestyle/xml.prefs

* More reformatting after rebasing

* Updated copyright header year (just to trigger build)

* Set travis timeout to 6 hours. Must be reverted after first build

* Make jar plugin include all xsd files

* Bump spotless to latest version

* Run maven with debug trace

* Attempt at getting travis to run

* Disabled formatting checks in travis temporarily
ConditionSummaryChargingGroup not referenced from ConditionSummaryStructure
…ingCalculationGroup

Fix annotation errors and align with definitions in NeTEx pt 3
Add ACCEPTED DRIVER PERMITS to VEHICEL TYpe
Copy link
Contributor

@skinkie skinkie left a comment

Choose a reason for hiding this comment

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

No, just no.

@Aurige
Copy link
Contributor

Aurige commented Jan 31, 2023

@nick the PR should be one (or a few lines) but you accidentally collect a lot of changes (mainly presentation/indentation) that create hundreds of small changes... so it is not easy to identify the real change, and there are a lot of unnecessary ones.

@nick-knowles
Copy link
Contributor Author

nick-knowles commented Jan 31, 2023 via email

@Aurige
Copy link
Contributor

Aurige commented Jan 31, 2023

Yes, the pretty print is most likely the issue (you can also tune it in preferences)
You can check your commits with Github Desktop: then you easily see if they focus on what you added, or if they come with a lot of additional unwanted changes.

@Aurige
Copy link
Contributor

Aurige commented Jan 31, 2023

Also, it's best for addition to start from "next" branch, not master.

@ue71603
Copy link
Contributor

ue71603 commented Nov 21, 2023

@skinkie can this one be closed?

@ue71603
Copy link
Contributor

ue71603 commented Dec 16, 2023

integrated into #612

@ue71603 ue71603 closed this Dec 16, 2023
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.

6 participants