Releases: amattu2/NHTSA-wrapper
Releases · amattu2/NHTSA-wrapper
v1.0.1 General Cleanup & Recall Endpoint Update
- Generalized code cleanup
- Updated the broken Recall Lookup API endpoint
Full Changelog: v1.0.0...v1.0.1
v1.0.0 Composer Support
Contributors
amattu2
Assets 2
v0.0.4b
New Engine String Format:
{Displacement as Liters/CC} {Cylinders} {Model} {Valve Design} {Fuel Type} {Fuel Injection Type} {Turbo}
Important changes were made to the way the engine description is produced. See below:
- If a primary fuel type is already specified in the engine description, don't add it again (i.e. with most GM products)
- Add fuel injection type if it is known (i.e. SGFI, MPFI, SFI, CRDI)
- Reordered engine attributes to make more sense
Additionally,
- Fixed inconsistent spacing between string concats
- Removed unneeded parenthesis around attributes (Turbo, Valve design, CC, Engine Model, etc)
v0.0.4
parseDecode VIN decoder improvements:
- Handle
Turboin Engine descriptions - Handle
BHP(Braking horse power rating) in Engine description - Ignore Engine cubic-centimeters (CC) in Engine description if the Liters is already included
- Handle
Body Classin vehicle Trim description
v0.0.3a (Breaking)
This is a major (breaking) change to the way NHTSA::decodeVIN returns the result. Instead of using the NHTSA "Variable Name", the "Variable ID" is used, which makes decoding and finding certain variables easier. Additionally, the Value ID is preserved for later use.
Old Design:
[] => Array
(
["Make"] => "DODGE"
...
)New Design:
[] => Array
...
[26] => Array
(
[Variable] => Make
[Value] => DODGE
[ValueId] => 476
)
...
)Additionally, this includes a substantial improvement for decoding Engine and Trim values, with additional features such a Fuel Type. Two new functions were introduced, both for parsing the aforementioned attributes (Engine/Trim).